Skip to main content
VulnerabilityPublished Updated

CVE-2024-47143: Linux kernel · dma-debug: fix a possible deadlock on radix_lock

Source GCVE Database

0
Compare

Not known to be exploited · CVSS 5.5 Medium.

Data as of 30 Oct 2026, 00:57 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 11 Jan 2025

  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

Until a fix is applied, avoid workloads or configurations that trigger the dma debug API while holding rq_lock, if possible.

Description

CVE-2024-47143 is a medium-severity vulnerability in the Linux kernel's dma-debug subsystem involving a potential deadlock on radix_lock. The issue arises because radix_lock() is held simultaneously with dma_hash_entry[idx].lock, creating a deadlock scenario when the dma debug API is called while holding rq_lock. This deadlock can occur in specific CPU contexts during memory management and hardware tracing operations. The fix involves reordering calls to avoid holding these locks simultaneously.

References

Community reviews

Loading reviews…