ring-buffer: Initialise reader page order in rb_allocate_cpu_buffer()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 7c620d89bae1a926ab7d626600285d3516c9f3c4, Kernel 2e37f2bf111429fbfa4d985b12df3ba496ca70aa, Kernel 3b3e0a6ee5bb3ac000f135beef26b2b7ed1a771a and 4 more.
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).
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=f9b94daa542a8d2532f0930f01cd9aec2d19621b <7c620d89bae1a926ab7d626600285d3516c9f3c4, >=f9b94daa542a8d2532f0930f01cd9aec2d19621b <2e37f2bf111429fbfa4d985b12df3ba496ca70aa, >=f9b94daa542a8d2532f0930f01cd9aec2d19621b <3b3e0a6ee5bb3ac000f135beef26b2b7ed1a771a, >=f9b94daa542a8d2532f0930f01cd9aec2d19621b <6d014e44b68ddd43f71288d2a4dbb1a259869149, =6.8 | 7c620d89bae1a926ab7d626600285d3516c9f3c4, 2e37f2bf111429fbfa4d985b12df3ba496ca70aa, 3b3e0a6ee5bb3ac000f135beef26b2b7ed1a771a, 6d014e44b68ddd43f71288d2a4dbb1a259869149 |
| linux-kernel: Kernel | >=6.19.0 <7.1.9, >=6.8.0 <6.12.105, >=6.13.0 <6.18.45 | 7.1.9, 6.12.105, 6.18.45 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket