CVE-2026-98342
dmaengine: wait for RCU readers before releasing dma_device
No known exploitation. EPSS puts it in the 7th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ 2ba05622b8b143b0c95968ba59bddfbd6d2f2559, < ac8ce9f89638d6d79875cca7d8ae42566a9bde15Upgrade to: ac8ce9f89638d6d79875cca7d8ae42566a9bde15Affected: ≥ 2ba05622b8b143b0c95968ba59bddfbd6d2f2559, < 14578c78405d51fa92e4ada4502a45f537c0fcb8Upgrade to: 14578c78405d51fa92e4ada4502a45f537c0fcb8Affected: ≥ 2ba05622b8b143b0c95968ba59bddfbd6d2f2559, < cbb3310a5167e868a5e763e32b9a23b4d50669eeUpgrade to: cbb3310a5167e868a5e763e32b9a23b4d50669eeAffected: ≥ 2ba05622b8b143b0c95968ba59bddfbd6d2f2559, < 8577a5ec4f7e00443015ef99f646def093121a1bUpgrade to: 8577a5ec4f7e00443015ef99f646def093121a1b + 4 more branchesStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
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.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 7th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/ac8ce9f89638d6d79875cca7d8ae42566a9bde15
- git.kernel.org/stable/c/14578c78405d51fa92e4ada4502a45f537c0fcb8
- git.kernel.org/stable/c/cbb3310a5167e868a5e763e32b9a23b4d50669ee
And 5 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI