CVE-2024-50138: bpf: Use raw_spinlock_t in ringbuf
bpf: Use rawspinlockt in ringbuf
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1 - Upgrade
Upgrade
debian/linux-6.1to a version that resolves this vulnerability.Fixed in 6.1.129-1~deb11u1 - Configuration
Switch the ringbuf spinlock from spinlock_t to raw_spinlock_t because __bpf_ringbuf_reserve is invoked from a tracepoint with preemption disabled.
BPF ringbuf spinlock type = raw_spinlock_t
Event History
Frequently Asked Questions
What is the severity of CVE-2024-50138?
CVE-2024-50138 is classified as a moderate severity vulnerability.
How do I fix CVE-2024-50138?
To fix CVE-2024-50138, users should upgrade to the latest patched version of the Linux kernel.
What software versions are affected by CVE-2024-50138?
CVE-2024-50138 affects Linux kernel versions from 5.8 to 6.1.115 and between 6.2 to 6.11.6, as well as 6.12-rc1, 6.12-rc2, and 6.12-rc3.
What is the nature of the vulnerability in CVE-2024-50138?
CVE-2024-50138 is related to the use of spinlock_t in a context that disables preemption, potentially causing sleep in atomic warnings.
Who can be impacted by CVE-2024-50138?
Users running the affected versions of the Linux kernel could be impacted by CVE-2024-50138.