CVE-2026-68466: mtd: rawnand: lpc32xx_slc: fail DMA transfer on completion timeout
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 17a8ce84964f243c8f89dc7353ac7e8d3137bc74, 307e4f4c1d4e1575b3495ecc6e41aa2adc40f491, 623c4d8e740debb4af28981e3d4e209f9d0260a4.
Low priority for now. Upgrade to Linux Linux 17a8ce84964f243c8f89dc7353ac7e8d3137bc74, 307e4f4c1d4e1575b3495ecc6e41aa2adc40f491, 623c4d8e740debb4af28981e3d4e209f9d0260a4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: mtd: rawnand: lpc32xx_slc: fail DMA transfer on completion timeout lpc32xx_xmit_dma() waits for the DMA completion callback but ignores wait_for_completion_timeout(). A timed out DMA transfer is therefore unmapped and reported as successful to the NAND read/write path. Return -ETIMEDOUT when the completion wait expires. Terminate the DMA channel before unmapping the scatterlist so the timed out transfer cannot continue to access the buffer after the error is returned.
- Published
- Aug 15, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- —
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.7affected
- 2944a44da09e46b6db2fd2c3334f242b09e05c43 and later · before 307e4f4c1d4e1575b3495ecc6e41aa2adc40f491affected · git
- 2944a44da09e46b6db2fd2c3334f242b09e05c43 and later · before c367af37ce7238c96c6071337149099467160746affected · git
- 2944a44da09e46b6db2fd2c3334f242b09e05c43 and later · before 623c4d8e740debb4af28981e3d4e209f9d0260a4affected · git
- 2944a44da09e46b6db2fd2c3334f242b09e05c43 and later · before bd4a622786f92e1f183f7557ab89dd32891cef60affected · git
- 2944a44da09e46b6db2fd2c3334f242b09e05c43 and later · before 8f5c3ee53a5dc1a0f7cfd780485f2c8b5d17f91daffected · git
- 2944a44da09e46b6db2fd2c3334f242b09e05c43 and later · before cf7258f57d18026b8f77c0e80ff1805e9caf7250affected · git
- 2944a44da09e46b6db2fd2c3334f242b09e05c43 and later · before cb2031f8b226efbd13735c07b075e5f14ec11f6daffected · git
- 2944a44da09e46b6db2fd2c3334f242b09e05c43 and later · before 17a8ce84964f243c8f89dc7353ac7e8d3137bc74affected · git
- before 3.7not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-68464Aug 15, 2026 · mmc: sdhci-esdhc-imx: disable irq during suspend to fix unhandled interrupt0Monitor
- ← EarlierCVE-2026-68465Aug 15, 2026 · mmc: sdhci-esdhc-imx: fix esdhc_change_pinstate() to allow default state restore0Monitor
- Later →CVE-2026-68467Aug 15, 2026 · mtd: mchp23k256: use SPI match data for chip caps31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 17a8ce84964f243c8f89dc7353ac7e8d3137bc74 | Vendor (CNA) |
| Linux Linux | 307e4f4c1d4e1575b3495ecc6e41aa2adc40f491 | Vendor (CNA) |
| Linux Linux | 623c4d8e740debb4af28981e3d4e209f9d0260a4 | Vendor (CNA) |
| Linux Linux | 8f5c3ee53a5dc1a0f7cfd780485f2c8b5d17f91d | Vendor (CNA) |
| Linux Linux | bd4a622786f92e1f183f7557ab89dd32891cef60 | Vendor (CNA) |
| Linux Linux | c367af37ce7238c96c6071337149099467160746 | Vendor (CNA) |
| Linux Linux | cb2031f8b226efbd13735c07b075e5f14ec11f6d | Vendor (CNA) |
| Linux Linux | cf7258f57d18026b8f77c0e80ff1805e9caf7250 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/307e4f4c1d4e1575b3495ecc6e41aa2adc40f491
- git.kernel.org/stable/c/623c4d8e740debb4af28981e3d4e209f9d0260a4
- git.kernel.org/stable/c/8f5c3ee53a5dc1a0f7cfd780485f2c8b5d17f91d
- git.kernel.org/stable/c/bd4a622786f92e1f183f7557ab89dd32891cef60
- git.kernel.org/stable/c/c367af37ce7238c96c6071337149099467160746
- git.kernel.org/stable/c/cb2031f8b226efbd13735c07b075e5f14ec11f6d
- git.kernel.org/stable/c/cf7258f57d18026b8f77c0e80ff1805e9caf7250
Vendor advisories and official records. Exploit/PoC links are deliberately left out.