Skip to main content
VulnerabilityPublished Updated

CVE-2024-56610: Linux kernel · kcsan: Turn report_filterlist_lock into a raw_spinlock

Source GCVE Database

0
Compare

Not known to be exploited · CVSS 5.5 Medium.

Data as of 30 Oct 2026, 00:50 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Dec 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

AI-suggested

A fix is available that converts the report_filterlist_lock to a raw_spinlock, preventing sleeping in atomic contexts. Users should update to a Linux kernel version that includes this fix. No additional mitigation is required as the patch addresses the root cause.

Description

CVE-2024-56610 addresses a concurrency issue in the Linux kernel's KCSAN (Kernel Concurrency Sanitizer) reporting logic. The vulnerability arises because the report_filterlist_lock was implemented as a non-raw spinlock, which may sleep on PREEMPT_RT kernels, causing invalid context bugs. The fix converts this lock to a raw_spinlock to prevent sleeping in atomic contexts. This change requires careful memory allocation strategies for the filter list to avoid concurrency issues during debugfs modifications.

References

Community reviews

Loading reviews…