Stale kernel-memory access via missing RCU grace period
Published Oct 6, 2026 · Updated Oct 6, 2026
A use-after-free in Linux dmaengine permits stale DMA device access when provider teardown races with pending-work traversal. dma_device_release() removes a device from the RCU list and frees it without waiting for readers in dma_issue_pending_all() to finish. The race requires concurrent provider removal and pending-work activity; the public patch establishes no attacker-controlled trigger or specific crash, disclosure, or code-execution outcome.
Summary
What happened
A use-after-free in Linux dmaengine permits stale DMA device access when provider teardown races with pending-work traversal. dma_device_release() removes a device from the RCU list and frees it without waiting for readers in dma_issue_pending_all() to finish. The race requires concurrent provider removal and pending-work activity; the public patch establishes no attacker-controlled trigger or specific crash, disclosure, or code-execution outcome.
The record
- CVE
- CVE-2026-98342
- Published
- Oct 6, 2026
- Updated
- Oct 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 6, 2026CVE publishedPublication date reported by the CVE source.
- Oct 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.29
- Affected versionversion=2ba05622b8b143b0c95968ba59bddfbd6d2f2559 <14578c78405d51fa92e4ada4502a45f537c0fcb8
- Affected versionversion=2ba05622b8b143b0c95968ba59bddfbd6d2f2559 <4448a539a0c39141cccc67be6cacde0f35024313
- Affected versionversion=2ba05622b8b143b0c95968ba59bddfbd6d2f2559 <4aed7e47a10b94ea3c5171e8d1382081accd2e03
- Affected versionversion=2ba05622b8b143b0c95968ba59bddfbd6d2f2559 <8577a5ec4f7e00443015ef99f646def093121a1b
- Affected versionversion=2ba05622b8b143b0c95968ba59bddfbd6d2f2559 <ac8ce9f89638d6d79875cca7d8ae42566a9bde15
- Affected versionversion=2ba05622b8b143b0c95968ba59bddfbd6d2f2559 <cbb3310a5167e868a5e763e32b9a23b4d50669ee
- Affected versionversion=2ba05622b8b143b0c95968ba59bddfbd6d2f2559 <dc750422170a563c7a81f6e49d36bb02c62ae37f
- Affected versionversion=2ba05622b8b143b0c95968ba59bddfbd6d2f2559 <fc1f4884f1d46fc7a8cee6e2997ecc9e8d1c7f77
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started