CyberRota Analysis
AI-GeneratedThe vulnerability affects the Linux kernel's ring buffer implementation, specifically in the `ring_buffer_alloc_read_page()` function, which can allocate a reader page with an outdated order due to a race condition with `ring_buffer_subbuf_order_set`. While the immediate impact is limited, as users can reallocate a new reader page, the potential for mismatched memory allocation poses a risk of data corruption or instability. Organizations using affected Linux kernel versions should prioritize addressing this issue to maintain system integrity and reliability.
Original NVD Description
In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Fix subbuf resize race with ring_buffer_alloc_read_page() ring_buffer_alloc_read_page() is racy with ring_buffer_subbuf_order_set, it can allocate a reader page with an outdated order. This isn't a big issue, the user can still re-allocate a new reader page and try again. However, what is more problematic is if the value of subbuf_order changes in the middle of ring_buffer_alloc_read_page(). In that case, bpage->order might not match the actual allocated memory. Use bpage->order for the allocation to prevent this race.