Kernel crash via uncleared DMA channel pointers
Published Jul 19, 2026 · Updated Jul 19, 2026
Invalid pointer dereference in the Linux QUP SPI driver allows attackers to crash the kernel after a DMA setup failure. spi_qup_init_dma() releases failed transmit and receive DMA channels without clearing their stored pointers, so later cleanup dereferences an error pointer or releases a channel twice. Reachability requires QUP SPI hardware, a failed DMA-channel request, and a later probe error or driver unbind; no data disclosure or modification is documented.
Summary
What happened
Invalid pointer dereference in the Linux QUP SPI driver allows attackers to crash the kernel after a DMA setup failure. spi_qup_init_dma() releases failed transmit and receive DMA channels without clearing their stored pointers, so later cleanup dereferences an error pointer or releases a channel twice. Reachability requires QUP SPI hardware, a failed DMA-channel request, and a later probe error or driver unbind; no data disclosure or modification is documented.
The record
- CVE
- CVE-2026-64170
- Published
- Jul 19, 2026
- Updated
- Jul 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jul 19, 2026CVE publishedPublication date reported by the CVE source.
- Jul 19, 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=4.1
- Affected versionversion=612762e82ae6058d69b4ce734598491bf030afe7 <0bb3bd442f0bdad3932739a61dd6c580c9c1955e
- Affected versionversion=612762e82ae6058d69b4ce734598491bf030afe7 <45760b72e84c1a1498f1a8a9047184c85299da20
- Affected versionversion=612762e82ae6058d69b4ce734598491bf030afe7 <4bb4764f2c51f03f657a28029eb0595d8223aab5
- Affected versionversion=612762e82ae6058d69b4ce734598491bf030afe7 <4f4051e9d644c371c50de4a042b85bba6727d5c3
- Affected versionversion=612762e82ae6058d69b4ce734598491bf030afe7 <8f9b61d255b1e989b8913b06c8ebe0aba5e1b238
- Affected versionversion=612762e82ae6058d69b4ce734598491bf030afe7 <9e673affb92c29d9ba879bf4ea81c5e840166b56
- Affected versionversion=612762e82ae6058d69b4ce734598491bf030afe7 <a7e8f3efd50a165ba0189f6dc57f7e51a7d149db
- Affected versionversion=612762e82ae6058d69b4ce734598491bf030afe7 <d577c55d189e7ae150973058d13e299b6855633f
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.
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