ring-buffer: Fix reader locking when changing the sub buffer order
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 09661f75e75cb6c1d2d8326a70c311d46729235f and Kernel a569290525a05162d5dd26d9845591eaf46e5802.
In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Fix reader locking when changing the sub buffer order The function ring_buffer_subbuf_order_set() updates each ring_buffer_per_cpu and installs new sub buffers that match the requested page order. This operation may be invoked concurrently with readers that rely on some of the modified data, such as the head bit (RB_PAGE_HEAD), or the ring_buffer_per_cpu.pages and reader_page pointers. However, no exclusive access is acquired by ring_buffer_subbuf_order_set(). Modifying the mentioned data while a reader also operates on them can then result in incorrect memory access and various crashes. Fix the problem by taking the reader_lock when updating a specific ring_buffer_per_cpu in ring_buffer_subbuf_order_set().
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.8, >=8e7b58c27b3c567316a51079b375b846f9223bba <09661f75e75cb6c1d2d8326a70c311d46729235f, >=8e7b58c27b3c567316a51079b375b846f9223bba <a569290525a05162d5dd26d9845591eaf46e5802 | 09661f75e75cb6c1d2d8326a70c311d46729235f, a569290525a05162d5dd26d9845591eaf46e5802 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket