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

Metrics

No CVSS v4.0

Attack Vector Local

Attack Complexity Low

Privileges Required Low

Scope Unchanged

Confidentiality Impact None

Integrity Impact None

Availability Impact High

User Interaction None

No CVSS v3.0

No CVSS v2

This CVE is not in the KEV list.

Key SSVC decision points have not yet been added.

Affected Vendors & Products

No data.

No data.

No data.

References
Link Providers
https://git.kernel.org/stable/c/3ccce34a5c3f5c9541108a451657ade621524b32 cve-icon cve-icon
https://git.kernel.org/stable/c/7543c3e3b9b88212fcd0aaf5cab5588797bdc7de cve-icon cve-icon
https://git.kernel.org/stable/c/8c1b4fea8d62285f5e1a8194889b39661608bd8a cve-icon cve-icon
https://git.kernel.org/stable/c/c212d91070beca0d03fef7bf988baf4ff4b3eee4 cve-icon cve-icon
https://git.kernel.org/stable/c/efe1b9bbf356357fdff0399af361133d6e3ba18e cve-icon cve-icon
https://git.kernel.org/stable/c/f2b95248a16c5186d1c658fc0aeb2f3bd95e5259 cve-icon cve-icon
https://lore.kernel.org/linux-cve-announce/2025011119-CVE-2024-47143-37ba@gregkh/T cve-icon
https://nvd.nist.gov/vuln/detail/CVE-2024-47143 cve-icon
https://www.cve.org/CVERecord?id=CVE-2024-47143 cve-icon
History

Tue, 14 Jan 2025 08:45:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

 cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Low

Sat, 11 Jan 2025 12:30:00 +0000

Type Values Removed Values Added
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().
Title dma-debug: fix a possible deadlock on radix_lock
References
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published: 2025-01-11T12:25:13.561Z

Updated: 2025-01-11T12:25:13.561Z

Reserved: 2025-01-09T09:49:29.749Z

Link: CVE-2024-47143

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2025-01-11T13:15:22.007

Modified: 2025-01-11T13:15:22.007

Link: CVE-2024-47143

cve-icon Redhat

Severity : Low

Publid Date: 2025-01-11T00:00:00Z

Links: CVE-2024-47143 - Bugzilla