Shellfeed logo Shellfeed

CVE-2026-98342 · UNKNOWN

Summary: dmaengine: wait for RCU readers before releasing dma_device

EPSS: 0.2% probability of exploitation in the next 30 days (percentile 7.3).

Details

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.

Affected packages

  • GIT git.kernel.org/pub/scm/linux/kernel/git/stable/linux [2ba05622b8b143b0c95968ba59bddfbd6d2f2559 – ac8ce9f89638d6d79875cca7d8ae42566a9bde15]
  • Linux Kernel [2.6.29 – 5.10.271] [5.11.0 – 5.15.222] [5.16.0 – 6.1.189] [6.2.0 – 6.6.158] [6.7.0 – 6.12.112] [6.13.0 – 6.18.54] [6.19.0 – 7.2.8]

References