AZL-56229
See a problem?- Import Source
- https://github.com/microsoft/AzureLinuxVulnerabilityData/blob/main/osv/AZL-56229.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/AZL-56229
- Upstream
- Published
- 2025-01-11T13:15:22Z
- Modified
- 2026-04-01T05:18:50.213077Z
- Severity
-
- 5.5 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
- Summary
- CVE-2024-47143 affecting package kernel for versions less than 5.15.176.3-1
- Details
-
In the Linux kernel, the following vulnerability has been resolved:
dma-debug: fix a possible deadlock on radix_lock
radixlock() shouldn't be held while holding dmahashentry[idx].lock otherwise, there's a possible deadlock scenario when dma debug API is called holding rqlock():
CPU0 CPU1 CPU2 dmafreeattrs() checkunmap() adddma_entry() _schedule() //out (A) rqlock() gethashbucket() (A) dmaentryhash checksync() (A) radixlock() (W) dmaentryhash dmaentryfree() (W) radixlock() // CPU2's one (W) rqlock()
CPU1 situation can happen when it extending radix tree and it tries to wake up kswapd via wakeallkswapd().
CPU2 situation can happen while perfeventtaskschedout() (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 dmaentryfree() after puthashbucket() in check_unmap().
- References