dma-debug: fix a possible deadlock on radix_lock
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().
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.231, 5.15.174, 6.1.120, 6.12.5, 6.6.66
- CVEs
- CVE-2024-47143
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 21:44 UTC · Revision 1
Source evidence
dma-debug: fix a possible deadlock on radix_lock
core-osv · Original sourcePublished 11 Jan 2025, 12:25 UTC
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().
osv:CVE-2024-47143
Kernel
Fixed versions: 5.10.231, 5.15.174, 6.1.120, 6.6.66, 6.12.5
Complete source record
{
"id": "b9ca60d8821d8f23a7bcab5af649f044a5ceac2e32f18990c637cc2d97addc12",
"url": "https://osv.dev/vulnerability/CVE-2024-47143",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "dma-debug: fix a possible deadlock on radix_lock",
"summary": "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().",
"evidence": "osv:CVE-2024-47143",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.10.231",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.174",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.120",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.66",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.5",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "medium",
"structured": {
"id": "CVE-2024-47143",
"aliases": [
"CVE-2024-47143"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "0abdd7a81b7e3fd781d7fabcca49501852bba17e"
},
{
"fixed": "3ccce34a5c3f5c9541108a451657ade621524b32"
},
{
"fixed": "efe1b9bbf356357fdff0399af361133d6e3ba18e"
},
{
"fixed": "8c1b4fea8d62285f5e1a8194889b39661608bd8a"
},
{
"fixed": "c212d91070beca0d03fef7bf988baf4ff4b3eee4"
},
{
"fixed": "f2b95248a16c5186d1c658fc0aeb2f3bd95e5259"
},
{
"fixed": "7543c3e3b9b88212fcd0aaf5cab5588797bdc7de"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-47143.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "3.14.0"
},
{
"fixed": "5.10.231"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.174"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.120"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.66"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.5"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-47143.json"
}
}
],
"modified": "2026-10-28T02:30:39.871510839Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/3ccce34a5c3f5c9541108a451657ade621524b32",
"https://git.kernel.org/stable/c/7543c3e3b9b88212fcd0aaf5cab5588797bdc7de",
"https://git.kernel.org/stable/c/8c1b4fea8d62285f5e1a8194889b39661608bd8a",
"https://git.kernel.org/stable/c/c212d91070beca0d03fef7bf988baf4ff4b3eee4",
"https://git.kernel.org/stable/c/efe1b9bbf356357fdff0399af361133d6e3ba18e",
"https://git.kernel.org/stable/c/f2b95248a16c5186d1c658fc0aeb2f3bd95e5259",
"https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html",
"https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/47xxx/CVE-2024-47143.json",
"https://nvd.nist.gov/vuln/detail/CVE-2024-47143",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/47xxx/CVE-2024-47143.json"
}
},
"related_cves": [
{
"value": "CVE-2024-47143",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 507375,
"published_at": "2025-01-11T12:25:13.561+00:00"
}