CyberRota Analysis
AI-GeneratedA vulnerability exists in the Linux kernel's ring-buffer implementation, where the reader page order is not properly initialized in the `rb_allocate_cpu_buffer()` function. This oversight could lead to improper handling of memory when freeing buffer pages, potentially causing instability or data corruption in systems using larger subbuffers. Linux system administrators and developers should prioritize addressing this issue to ensure the stability and reliability of their applications.
Original NVD Description
In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Initialise reader page order in rb_allocate_cpu_buffer() In rb_allocate_cpu_buffer(), bpage->order was omitted, leaving it as 0. This is an issue for a ring-buffer with subbufs bigger than PAGE_SIZE if when freed: free_buffer_page() relies on this value. Align the value with the actual allocation size (buffer::subbuf_order).