CVE-2024-50138: bpf: Use raw_spinlock_t in ringbuf
First published: Tue Nov 05 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: bpf: Use raw_spinlock_t in ringbuf The function __bpf_ringbuf_reserve is invoked from a tracepoint, which disables preemption. Using spinlock_t in this context can lead to a "sleep in atomic" warning in the RT variant. This issue is illustrated in the example below: BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48 in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 556208, name: test_progs preempt_count: 1, expected: 0 RCU nest depth: 1, expected: 1 INFO: lockdep is turned off. Preemption disabled at: [<ffffd33a5c88ea44>] migrate_enable+0xc0/0x39c CPU: 7 PID: 556208 Comm: test_progs Tainted: G Hardware name: Qualcomm SA8775P Ride (DT) Call trace: dump_backtrace+0xac/0x130 show_stack+0x1c/0x30 dump_stack_lvl+0xac/0xe8 dump_stack+0x18/0x30 __might_resched+0x3bc/0x4fc rt_spin_lock+0x8c/0x1a4 __bpf_ringbuf_reserve+0xc4/0x254 bpf_ringbuf_reserve_dynptr+0x5c/0xdc bpf_prog_ac3d15160d62622a_test_read_write+0x104/0x238 trace_call_bpf+0x238/0x774 perf_call_bpf_enter.isra.0+0x104/0x194 perf_syscall_enter+0x2f8/0x510 trace_sys_enter+0x39c/0x564 syscall_trace_enter+0x220/0x3c0 do_el0_svc+0x138/0x1dc el0_svc+0x54/0x130 el0t_64_sync_handler+0x134/0x150 el0t_64_sync+0x17c/0x180 Switch the spinlock to raw_spinlock_t to avoid this error.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | >=5.8<6.1.115 | |
| Linux Kernel | >=6.2<6.11.6 | |
| Linux Kernel | =6.12-rc1 | |
| Linux Kernel | =6.12-rc2 | |
| Linux Kernel | =6.12-rc3 | |
| debian/linux | <=5.10.223-1<=5.10.226-1 | 6.1.123-1 6.1.128-1 6.12.12-1 6.12.15-1 |
| debian/linux-6.1 | 6.1.119-1~deb11u1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/5eb34999d118e69a20dc0c6556f315fcb0a1f8d3
- https://git.kernel.org/stable/c/ca30e682e5d6de44d12c4610767811c9a21d59ba
- https://git.kernel.org/stable/c/8b62645b09f870d70c7910e7550289d444239a46
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50138
- https://nvd.nist.gov/vuln/detail/CVE-2024-50138
- https://launchpad.net/bugs/cve/CVE-2024-50138
- https://security-tracker.debian.org/tracker/CVE-2024-50138
- https://ubuntu.com/security/CVE-2024-50138
- https://git.kernel.org/linus/8b62645b09f870d70c7910e7550289d444239a46
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.
- agent/type
- agent/title
- agent/first-publish-date
- agent/author
- agent/severity
- agent/remedy
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/usn-cve
- source/Ubuntu
- collector/security-tracker-debian
- source/Debian
- agent/references
- agent/source
- agent/softwarecombine
- agent/tags
- agent/description
- agent/event
- vendor/linux
- canonical/linux kernel
- version/linux kernel/5.8
- version/linux kernel/6.2
- version/linux kernel/6.12-rc1
- version/linux kernel/6.12-rc2
- version/linux kernel/6.12-rc3
- package-manager/debian