CVE-2026-98342: Linux kernel · dmaengine: wait for RCU readers before releasing dma_device
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in fc1f4884f1d46fc7a8cee6e2997ecc9e8d1c7f77 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 14:05 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in fc1f4884f1d46fc7a8cee6e2997ecc9e8d1c7f77, dc750422170a563c7a81f6e49d36bb02c62ae37f, cbb3310a5167e868a5e763e32b9a23b4d50669ee +5
Exploitation evidence
Disclosed: evidence found.
CVE published 6 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in the Linux kernel. Users should update to a kernel version that includes the fix identified by commit hashes such as fc1f4884f1d46fc7a8cee6e2997ecc9e8d1c7f77 and others listed. No additional mitigation is required beyond applying the official patch.
Description
A use-after-free vulnerability in the Linux kernel's dmaengine subsystem was fixed by adding a synchronize_rcu() call before freeing dma_device structures. The issue arose because dma_device_release() could free a device while concurrent RCU readers were still accessing it, leading to potential memory corruption.
References
- git.kernel.org/stable/c/ac8ce9f89638d6d79875cca7d8ae42566a9bde15 (opens in a new tab)
- git.kernel.org/stable/c/14578c78405d51fa92e4ada4502a45f537c0fcb8 (opens in a new tab)
- git.kernel.org/stable/c/cbb3310a5167e868a5e763e32b9a23b4d50669ee (opens in a new tab)
- git.kernel.org/stable/c/8577a5ec4f7e00443015ef99f646def093121a1b (opens in a new tab)
- git.kernel.org/stable/c/4448a539a0c39141cccc67be6cacde0f35024313 (opens in a new tab)
- git.kernel.org/stable/c/fc1f4884f1d46fc7a8cee6e2997ecc9e8d1c7f77 (opens in a new tab)
- git.kernel.org/stable/c/4aed7e47a10b94ea3c5171e8d1382081accd2e03 (opens in a new tab)
- git.kernel.org/stable/c/dc750422170a563c7a81f6e49d36bb02c62ae37f (opens in a new tab)