dma-debug: fix a possible deadlock on radix_lock
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 0abdd7a81b7e3fd781d7fabcca49501852bba17e · < 7543c3e3b9b88212fcd0aaf5cab5588797bdc7de| No fix yet |
| Linux Linux |
|
|
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().
From the CVE record · Linux
The Linux kernel's dma-debug code can deadlock because of the order in which it acquires radix_lock and a DMA hash-entry lock. This can occur when DMA debug operations overlap with scheduling and radix-tree extension; the input does not establish an attacker path, authentication requirement, or user interaction.
Engineers running Linux kernels with dma-debug should check their kernel versions against the vendor advisory; affected versions are not specified.