Kernel memory corruption via DMA timeout mishandling
Published Aug 15, 2026 · Updated Aug 15, 2026
DMA timeout mishandling in the LPC32xx SLC NAND driver in Linux allows local users to corrupt kernel memory during NAND I/O. lpc32xx_xmit_dma() ignores the result of wait_for_completion_timeout(), unmaps a timed-out transfer, reports success, and leaves DMA able to access the buffer after it is unmapped. The path requires LPC32xx SLC NAND hardware and locally initiated flash access; continued DMA can disclose or overwrite kernel data, corrupt flash contents, or crash the system.
Summary
What happened
DMA timeout mishandling in the LPC32xx SLC NAND driver in Linux allows local users to corrupt kernel memory during NAND I/O. lpc32xx_xmit_dma() ignores the result of wait_for_completion_timeout(), unmaps a timed-out transfer, reports success, and leaves DMA able to access the buffer after it is unmapped. The path requires LPC32xx SLC NAND hardware and locally initiated flash access; continued DMA can disclose or overwrite kernel data, corrupt flash contents, or crash the system.
The record
- CVE
- CVE-2026-68466
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 15, 2026CVE publishedPublication date reported by the CVE source.
- Aug 15, 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=2944a44da09e46b6db2fd2c3334f242b09e05c43 <17a8ce84964f243c8f89dc7353ac7e8d3137bc74
- Affected versionversion=2944a44da09e46b6db2fd2c3334f242b09e05c43 <307e4f4c1d4e1575b3495ecc6e41aa2adc40f491
- Affected versionversion=2944a44da09e46b6db2fd2c3334f242b09e05c43 <623c4d8e740debb4af28981e3d4e209f9d0260a4
- Affected versionversion=2944a44da09e46b6db2fd2c3334f242b09e05c43 <8f5c3ee53a5dc1a0f7cfd780485f2c8b5d17f91d
- Affected versionversion=2944a44da09e46b6db2fd2c3334f242b09e05c43 <bd4a622786f92e1f183f7557ab89dd32891cef60
- Affected versionversion=2944a44da09e46b6db2fd2c3334f242b09e05c43 <c367af37ce7238c96c6071337149099467160746
- Affected versionversion=2944a44da09e46b6db2fd2c3334f242b09e05c43 <cb2031f8b226efbd13735c07b075e5f14ec11f6d
- Affected versionversion=2944a44da09e46b6db2fd2c3334f242b09e05c43 <cf7258f57d18026b8f77c0e80ff1805e9caf7250
- Affected versionversion=3.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo