ring-buffer: Fix subbuf resize race with ring_buffer_alloc_read_page()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel e743527c5bfdceda1095bc0a9e596e2aebb6a9c3, Kernel 2313ff69bd237aad264a5913907f374f958335a2, Kernel 2dc510957fe8fd098ab3c3147ebdf34d00cd2734 and 4 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=bce761d757452ba5eb77e11fecc37a04b67494e7 <e743527c5bfdceda1095bc0a9e596e2aebb6a9c3, >=bce761d757452ba5eb77e11fecc37a04b67494e7 <2313ff69bd237aad264a5913907f374f958335a2, >=bce761d757452ba5eb77e11fecc37a04b67494e7 <2dc510957fe8fd098ab3c3147ebdf34d00cd2734, >=bce761d757452ba5eb77e11fecc37a04b67494e7 <53106e9262a310ef2c9a9321168c03705940c678, =6.8 | e743527c5bfdceda1095bc0a9e596e2aebb6a9c3, 2313ff69bd237aad264a5913907f374f958335a2, 2dc510957fe8fd098ab3c3147ebdf34d00cd2734, 53106e9262a310ef2c9a9321168c03705940c678 |
| linux-kernel: Kernel | >=6.19.0 <7.2.4, >=6.8.0 <6.12.112, >=6.13.0 <6.18.50 | 7.2.4, 6.12.112, 6.18.50 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket