CVE-2024-47143: dma-debug: fix a possible deadlock on radix_lock
First published: Sat Jan 11 2025(Updated: )
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().
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | ||
| Linux Kernel | <5.10.231 | |
| Linux Kernel | >=5.11<5.15.174 | |
| Linux Kernel | >=5.16<6.1.120 | |
| Linux Kernel | >=6.2<6.6.66 | |
| Linux Kernel | >=6.7<6.12.5 | |
| debian/linux | <=5.10.223-1 | 5.10.234-1 6.1.129-1 6.1.133-1 6.12.22-1 |
| debian/linux-6.1 | 6.1.129-1~deb11u1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/3ccce34a5c3f5c9541108a451657ade621524b32
- https://git.kernel.org/stable/c/efe1b9bbf356357fdff0399af361133d6e3ba18e
- https://git.kernel.org/stable/c/8c1b4fea8d62285f5e1a8194889b39661608bd8a
- https://git.kernel.org/stable/c/c212d91070beca0d03fef7bf988baf4ff4b3eee4
- https://git.kernel.org/stable/c/f2b95248a16c5186d1c658fc0aeb2f3bd95e5259
- https://git.kernel.org/stable/c/7543c3e3b9b88212fcd0aaf5cab5588797bdc7de
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47143
- https://nvd.nist.gov/vuln/detail/CVE-2024-47143
- https://launchpad.net/bugs/cve/CVE-2024-47143
- https://security-tracker.debian.org/tracker/CVE-2024-47143
- https://ubuntu.com/security/CVE-2024-47143
- https://git.kernel.org/linus/7543c3e3b9b88212fcd0aaf5cab5588797bdc7de
Frequently Asked Questions
What is the severity of CVE-2024-47143?
CVE-2024-47143 has a moderate severity due to its potential to cause deadlocks in the Linux kernel.
How do I fix CVE-2024-47143?
To fix CVE-2024-47143, upgrade to a version of the Linux kernel that is patched beyond 5.10.231.
What software is affected by CVE-2024-47143?
CVE-2024-47143 affects multiple versions of the Linux kernel ranging from 5.11 to 6.12.5.
Can CVE-2024-47143 cause system crashes?
Yes, CVE-2024-47143 can lead to potential deadlocks, which could result in system crashes.
Is CVE-2024-47143 generally exploitable?
Exploitation of CVE-2024-47143 is primarily dependent on specific conditions related to the use of the dma debug API.
- agent/title
- agent/type
- agent/first-publish-date
- agent/author
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/last-modified-date
- agent/remedy
- agent/severity
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/nvd-api
- source/NVD
- collector/usn-cve
- source/Ubuntu
- collector/launchpad-cve
- source/Launchpad
- agent/references
- agent/description
- agent/source
- agent/softwarecombine
- agent/tags
- agent/event
- collector/security-tracker-debian
- source/Debian
- collector/nvd-cve
- vendor/linux
- canonical/linux kernel
- version/linux kernel/5.11
- version/linux kernel/5.16
- version/linux kernel/6.2
- version/linux kernel/6.7
- package-manager/debian