First published: Fri Nov 08 2024(Updated: )
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().
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | >=6.8<6.11.6 | |
Linux Kernel | =6.12-rc1 | |
Linux Kernel | =6.12-rc2 | |
Linux Kernel | =6.12-rc3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-50207 has not been assigned a CVSS score yet, indicating its impact is still being assessed.
To fix CVE-2024-50207, update your Linux kernel to version 6.11.6 or above.
CVE-2024-50207 affects Linux kernel versions between 6.8 and 6.11.6, as well as 6.12-rc1, 6.12-rc2, and 6.12-rc3.
Currently, there are no known workarounds for CVE-2024-50207 other than updating the kernel.
CVE-2024-50207 impacts the ring-buffer functionality related to reader locking during sub buffer order changes.