CVE-2024-50207: ring-buffer: Fix reader locking when changing the sub buffer order
In the Linux kernel, the following vulnerability has been resolved:
ring-buffer: Fix reader locking when changing the sub buffer order
The function ringbuffersubbuforderset() updates each ringbufferpercpu 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 (RBPAGEHEAD), or the ringbufferpercpu.pages and readerpage pointers. However, no exclusive access is acquired by ringbuffersubbuforderset(). 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 readerlock when updating a specific ringbufferpercpu in ringbuffersubbuforderset().
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.22-1Fixed in 6.12.25-1
Event History
Frequently Asked Questions
What is the severity of CVE-2024-50207?
CVE-2024-50207 has not been assigned a CVSS score yet, indicating its impact is still being assessed.
How do I fix CVE-2024-50207?
To fix CVE-2024-50207, update your Linux kernel to version 6.11.6 or above.
Which versions of the Linux kernel are affected by CVE-2024-50207?
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.
Is there a workaround for CVE-2024-50207?
Currently, there are no known workarounds for CVE-2024-50207 other than updating the kernel.
What specific component of the Linux kernel is impacted by CVE-2024-50207?
CVE-2024-50207 impacts the ring-buffer functionality related to reader locking during sub buffer order changes.