Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 3ccce34a5c3f5c9541108a451657ade621524b32, 7543c3e3b9b88212fcd0aaf5cab5588797bdc7de, 8c1b4fea8d62285f5e1a8194889b39661608bd8a; azl3 kernel 6.6.64.2-9 on Azure Linux 3.0 6.6.76.1-1; azl3 kernel 6.6.76.1-1 on Azure Linux 3.0 6.6.76.1-1.

Low priority for now. Upgrade to Linux Linux 3ccce34a5c3f5c9541108a451657ade621524b32, 7543c3e3b9b88212fcd0aaf5cab5588797bdc7de, 8c1b4fea8d62285f5e1a8194889b39661608bd8a; azl3 kernel 6.6.64.2-9 on Azure Linux 3.0 6.6.76.1-1; azl3 kernel 6.6.76.1-1 on Azure Linux 3.0 6.6.76.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: dma-debug: fix a possible deadlock on radix_lock radix_lock() shouldn't be held while holding dma_hash_entry[idx].lock otherwise, there's a possible deadlock scenario when dma debug API is called holding rq_lock(): CPU0 CPU1 CPU2 dma_free_attrs() check_unmap() add_dma_entry() __schedule() //out (A) rq_lock() get_hash_bucket() (A) dma_entry_hash check_sync() (A) radix_lock() (W) dma_entry_hash dma_entry_free() (W) radix_lock() // CPU2's one (W) rq_lock() CPU1 situation can happen when it extending radix tree and it tries to wake up kswapd via wake_all_kswapd(). CPU2 situation can happen while perf_event_task_sched_out() (i.e. dma sync operation is called while deleting perf_event using etm and etr tmc which are Arm Coresight hwtracing driver backends). To remove this possible situation, call dma_entry_free() after put_hash_bucket() in check_unmap().

Published
Jan 11, 2025
Updated
Jun 17, 2026
EPSS
0.1% · 8th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-47143

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 3.14affected
    • 0abdd7a81b7e3fd781d7fabcca49501852bba17e and later · before 3ccce34a5c3f5c9541108a451657ade621524b32affected · git
    • 0abdd7a81b7e3fd781d7fabcca49501852bba17e and later · before efe1b9bbf356357fdff0399af361133d6e3ba18eaffected · git
    • 0abdd7a81b7e3fd781d7fabcca49501852bba17e and later · before 8c1b4fea8d62285f5e1a8194889b39661608bd8aaffected · git
    • 0abdd7a81b7e3fd781d7fabcca49501852bba17e and later · before c212d91070beca0d03fef7bf988baf4ff4b3eee4affected · git
    • 0abdd7a81b7e3fd781d7fabcca49501852bba17e and later · before f2b95248a16c5186d1c658fc0aeb2f3bd95e5259affected · git
    • 0abdd7a81b7e3fd781d7fabcca49501852bba17e and later · before 7543c3e3b9b88212fcd0aaf5cab5588797bdc7deaffected · git
    • before 3.14not affected · semver
    • 5.10.231 and later · up to and including 5.10.*not affected · semver
    • 5.15.174 and later · up to and including 5.15.*not affected · semver
Affected versions · NVD (5)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernelbefore 5.10.231
  • linux linux kernel5.11 and later · before 5.15.174
  • linux linux kernel5.16 and later · before 6.1.120
  • linux linux kernel6.2 and later · before 6.6.66
  • linux linux kernel6.7 and later · before 6.12.5

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.123-16.1.123-1
Debian:13linuxbefore 6.12.5-16.12.5-1
openSUSE:Leap 15.6dtb-aarch64before 6.4.0-150600.23.38.16.4.0-150600.23.38.1
openSUSE:Leap 15.6kernel-64kbbefore 6.4.0-150600.23.38.16.4.0-150600.23.38.1
openSUSE:Leap 15.6kernel-azurebefore 6.4.0-150600.8.26.16.4.0-150600.8.26.1
openSUSE:Leap 15.6kernel-debugbefore 6.4.0-150600.23.38.16.4.0-150600.23.38.1
openSUSE:Leap 15.6kernel-defaultbefore 6.4.0-150600.23.38.16.4.0-150600.23.38.1
openSUSE:Leap 15.6kernel-default-basebefore 6.4.0-150600.23.38.1.150600.12.16.26.4.0-150600.23.38.1.150600.12.16.2
openSUSE:Leap 15.6kernel-docsbefore 6.4.0-150600.23.38.16.4.0-150600.23.38.1
openSUSE:Leap 15.6kernel-kvmsmallbefore 6.4.0-150600.23.38.16.4.0-150600.23.38.1
openSUSE:Leap 15.6kernel-obs-buildbefore 6.4.0-150600.23.38.16.4.0-150600.23.38.1
openSUSE:Leap 15.6kernel-obs-qabefore 6.4.0-150600.23.38.16.4.0-150600.23.38.1
openSUSE:Leap 15.6kernel-rtbefore 6.4.0-150600.10.26.16.4.0-150600.10.26.1
openSUSE:Leap 15.6kernel-rt_debugbefore 6.4.0-150600.10.26.16.4.0-150600.10.26.1
openSUSE:Leap 15.6kernel-sourcebefore 6.4.0-150600.23.38.16.4.0-150600.23.38.1
openSUSE:Leap 15.6kernel-source-azurebefore 6.4.0-150600.8.26.16.4.0-150600.8.26.1
openSUSE:Leap 15.6kernel-source-rtbefore 6.4.0-150600.10.26.16.4.0-150600.10.26.1
openSUSE:Leap 15.6kernel-symsbefore 6.4.0-150600.23.38.16.4.0-150600.23.38.1
openSUSE:Leap 15.6kernel-syms-azurebefore 6.4.0-150600.8.26.16.4.0-150600.8.26.1
openSUSE:Leap 15.6kernel-syms-rtbefore 6.4.0-150600.10.26.16.4.0-150600.10.26.1
openSUSE:Leap 15.6kernel-zfcpdumpbefore 6.4.0-150600.23.38.16.4.0-150600.23.38.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_8before 1-150600.13.3.21-150600.13.3.2
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6-RT_Update_8before 1-150600.1.3.11-150600.1.3.1
SUSE:Linux Enterprise Module for Basesystem 15 SP6kernel-64kbbefore 6.4.0-150600.23.38.16.4.0-150600.23.38.1

+19

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-45828Jan 11, 2025 · i3c: mipi-i3c-hci: Mask ring interrupts before ring stop request
    22Monitor
  • ← EarlierCVE-2024-46896Jan 11, 2025 · drm/amdgpu: don't access invalid sched
    22Monitor
  • Later →CVE-2024-48873Jan 11, 2025 · wifi: rtw89: check return value of ieee80211_probereq_get() for RNR
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux3ccce34a5c3f5c9541108a451657ade621524b32Vendor (CNA)
Linux Linux7543c3e3b9b88212fcd0aaf5cab5588797bdc7deVendor (CNA)
Linux Linux8c1b4fea8d62285f5e1a8194889b39661608bd8aVendor (CNA)
Linux Linuxc212d91070beca0d03fef7bf988baf4ff4b3eee4Vendor (CNA)
Linux Linuxefe1b9bbf356357fdff0399af361133d6e3ba18eVendor (CNA)
Linux Linuxf2b95248a16c5186d1c658fc0aeb2f3bd95e5259Vendor (CNA)
azl3 kernel 6.6.64.2-9 on Azure Linux 3.06.6.76.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.76.1-1 on Azure Linux 3.06.6.76.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.173.1-2 on CBL Mariner 2.05.15.176.3-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.173.1-2 on CBL-Mariner 2.05.15.176.3-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.176.3-1 on CBL Mariner 2.05.15.176.3-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.123-1 · Debian:12Package registry (OSV)
opensuse:dtb-aarch646.4.0-150600.23.38.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-64kb6.4.0-150600.23.38.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-azure6.4.0-150600.8.26.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-debug6.4.0-150600.23.38.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-default6.4.0-150600.23.38.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-default-base6.4.0-150600.23.38.1.150600.12.16.2 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-docs6.4.0-150600.23.38.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-kvmsmall6.4.0-150600.23.38.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-obs-build6.4.0-150600.23.38.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-obs-qa6.4.0-150600.23.38.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-source-azure6.4.0-150600.8.26.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-syms-azure6.4.0-150600.8.26.1 · openSUSE:Leap 15.6Package registry (OSV)
suse:kernel-64kb6.4.0-150600.23.38.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6Package registry (OSV)
suse:kernel-azure6.4.0-150600.8.26.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP6Package registry (OSV)
suse:kernel-default6.4.0-150600.23.38.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6Package registry (OSV)
suse:kernel-default-base6.4.0-150600.23.38.1.150600.12.16.2 · SUSE:Linux Enterprise Module for Basesystem 15 SP6Package registry (OSV)
suse:kernel-docs6.4.0-150600.23.38.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP6Package registry (OSV)
suse:kernel-livepatch-SLE15-SP6_Update_81-150600.13.3.2 · SUSE:Linux Enterprise Live Patching 15 SP6Package registry (OSV)

+6

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-667 · Improper Locking

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records