نسخههای متأثر
- نسخههای متأثر
- نامشخص
- نسخهٔ اصلاحشده
- اعلام نشده
بهرهبرداری
شرح آسیبپذیری
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.
A flaw was found in the Linux kernel's ring-buffer component. A race condition exists in the ring_buffer_alloc_read_page() function when it interacts with ring_buffer_subbuf_order_set. This can lead to an incorrect memory allocation where the buffer page's order (bpage->order) does not match the actual allocated memory. This mismatch could potentially cause system instability or a denial of service.

