dmaengine: wait for RCU readers before releasing dma_device
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 2ba05622b8b143b0c95968ba59bddfbd6d2f2559 · < fc1f4884f1d46fc7a8cee6e2997ecc9e8d1c7f77| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
dmaengine: wait for RCU readers before releasing dma_device
dma_issue_pending_all() walks the dma_device_list with list_for_each_entry_rcu() under rcu_read_lock(). dma_device_release() unlinks the device with list_del_rcu() and then calls device->device_release() (which in many drivers, such as plx_dma.c, directly calls kfree()).
Because there is no grace period between unlinking the device and freeing it, concurrent RCU readers in dma_issue_pending_all() can access the device after it has been freed.
The lockless walk originally relied on clients holding a dmaengine reference to pin the provider module, and therefore the device, for as long as they might traverse the list. Commit 8ad342a86359 ("dmaengine: Add reference counting to dma_device struct") decoupled the dma_device lifetime from the module reference, so the device can now be released while a reader is still walking the list.
Add synchronize_rcu() before the device is freed, so RCU readers are guaranteed to have finished. Keep it unconditional: providers that do not implement device_release() free the device themselves once dma_async_device_unregister() returns. This call will delay for a grace period with dma_list_mutex held, which is safe and only teardown path is delayed.
From the CVE record · Linux
The Linux kernel’s dmaengine subsystem can free a DMA device while an RCU reader is still accessing it. A concurrent device teardown and dma_issue_pending_all() traversal can therefore cause a use-after-free. The input does not specify whether an attacker can trigger this, or any network, authentication, or user-interaction requirements.
Engineers running Linux kernels with the affected dmaengine code should check their kernel versions against the vendor advisory; affected versions are not listed in the input.