- Vulnerability/
- CVE-2024-56610
CVE-2024-56610: kcsan: Turn report_filterlist_lock into a raw_spinlock
First published: Fri Dec 27 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: kcsan: Turn report_filterlist_lock into a raw_spinlock Ran Xiaokai reports that with a KCSAN-enabled PREEMPT_RT kernel, we can see splats like: | BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48 | in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 0, name: swapper/1 | preempt_count: 10002, expected: 0 | RCU nest depth: 0, expected: 0 | no locks held by swapper/1/0. | irq event stamp: 156674 | hardirqs last enabled at (156673): [<ffffffff81130bd9>] do_idle+0x1f9/0x240 | hardirqs last disabled at (156674): [<ffffffff82254f84>] sysvec_apic_timer_interrupt+0x14/0xc0 | softirqs last enabled at (0): [<ffffffff81099f47>] copy_process+0xfc7/0x4b60 | softirqs last disabled at (0): [<0000000000000000>] 0x0 | Preemption disabled at: | [<ffffffff814a3e2a>] paint_ptr+0x2a/0x90 | CPU: 1 UID: 0 PID: 0 Comm: swapper/1 Not tainted 6.11.0+ #3 | Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org 04/01/2014 | Call Trace: | <IRQ> | dump_stack_lvl+0x7e/0xc0 | dump_stack+0x1d/0x30 | __might_resched+0x1a2/0x270 | rt_spin_lock+0x68/0x170 | kcsan_skip_report_debugfs+0x43/0xe0 | print_report+0xb5/0x590 | kcsan_report_known_origin+0x1b1/0x1d0 | kcsan_setup_watchpoint+0x348/0x650 | __tsan_unaligned_write1+0x16d/0x1d0 | hrtimer_interrupt+0x3d6/0x430 | __sysvec_apic_timer_interrupt+0xe8/0x3a0 | sysvec_apic_timer_interrupt+0x97/0xc0 | </IRQ> On a detected data race, KCSAN's reporting logic checks if it should filter the report. That list is protected by the report_filterlist_lock *non-raw* spinlock which may sleep on RT kernels. Since KCSAN may report data races in any context, convert it to a raw_spinlock. This requires being careful about when to allocate memory for the filter list itself which can be done via KCSAN's debugfs interface. Concurrent modification of the filter list via debugfs should be rare: the chosen strategy is to optimistically pre-allocate memory before the critical section and discard if unused.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | ||
| debian/linux | <=5.10.223-1 | 5.10.234-1 6.1.129-1 6.1.133-1 6.12.22-1 |
| debian/linux-6.1 | 6.1.129-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/0ab4951c1473c7d1ceaf1232eb927109cd1c4859
- https://git.kernel.org/stable/c/59458fa4ddb47e7891c61b4a928d13d5f5b00aa0
- https://git.kernel.org/stable/c/889a0d3a35fdedba1c5dcb6410c95c32421680ec
- https://git.kernel.org/stable/c/dca4e74a918586913d251c0b359e8cc96a3883ea
- https://git.kernel.org/stable/c/ea6588abcc15d68fdeae777ffe3dd74c02eab407
- https://git.kernel.org/stable/c/f4f2ef66d288ea796ddb8ecbdc2df074ab2d5f4d
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-56610
- https://nvd.nist.gov/vuln/detail/CVE-2024-56610
- https://launchpad.net/bugs/cve/CVE-2024-56610
- https://security-tracker.debian.org/tracker/CVE-2024-56610
- https://ubuntu.com/security/CVE-2024-56610
- https://git.kernel.org/linus/59458fa4ddb47e7891c61b4a928d13d5f5b00aa0
Frequently Asked Questions
What is the severity of CVE-2024-56610?
CVE-2024-56610 is considered a high-severity vulnerability due to its impact on kernel stability in KCSAN-enabled PREEMPT_RT environments.
How do I fix CVE-2024-56610?
To fix CVE-2024-56610, update your Linux kernel to the latest stable version where this vulnerability has been patched.
What systems are affected by CVE-2024-56610?
CVE-2024-56610 affects Linux kernels that are compiled with KCSAN and PREEMPT_RT enabled.
What kind of exploit is associated with CVE-2024-56610?
CVE-2024-56610 could be exploited to cause kernel crashes or unexpected behavior due to improper locking mechanisms.
Who reported the CVE-2024-56610 vulnerability?
The vulnerability CVE-2024-56610 was reported by Ran Xiaokai.
- agent/title
- agent/severity
- agent/type
- agent/first-publish-date
- collector/nvd-api
- source/NVD
- agent/author
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/guess-ai
- agent/software-canonical-lookup
- collector/nvd-cve
- collector/launchpad-cve
- source/Launchpad
- agent/references
- agent/source
- agent/softwarecombine
- agent/tags
- agent/description
- agent/event
- collector/usn-cve
- source/Ubuntu
- collector/security-tracker-debian
- source/Debian
- vendor/linux
- canonical/linux kernel
- package-manager/debian