Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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().

Timeline

  1. ID reserved

    By Linux

  2. · 2 days later

    Published

  3. · 16 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-47143, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.19% · top 91% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 0abdd7a81b7e3fd781d7fabcca49501852bba17e – < 3ccce34a5c3f5c9541108a451657ade621524b32
    • affected 0abdd7a81b7e3fd781d7fabcca49501852bba17e – < efe1b9bbf356357fdff0399af361133d6e3ba18e
    • affected 0abdd7a81b7e3fd781d7fabcca49501852bba17e – < 8c1b4fea8d62285f5e1a8194889b39661608bd8a
    • affected 0abdd7a81b7e3fd781d7fabcca49501852bba17e – < c212d91070beca0d03fef7bf988baf4ff4b3eee4
    • affected 0abdd7a81b7e3fd781d7fabcca49501852bba17e – < f2b95248a16c5186d1c658fc0aeb2f3bd95e5259
    • affected 0abdd7a81b7e3fd781d7fabcca49501852bba17e – < 7543c3e3b9b88212fcd0aaf5cab5588797bdc7de
  • Linux · Linux

    • affected 3.14
    • unaffected < 3.14
    • unaffected 5.10.231 – ≤ 5.10.*
    • unaffected 5.15.174 – ≤ 5.15.*
    • unaffected 6.1.120 – ≤ 6.1.*
    • unaffected 6.6.66 – ≤ 6.6.*
    • unaffected 6.12.5 – ≤ 6.12.*
    • unaffected 6.13 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-47143 badge
[![CVE-2024-47143](https://cveledger.app/badge/CVE-2024-47143.svg)](https://cveledger.app/cve/CVE-2024-47143)

Record last updated .