Skip to main content
VulnerabilityPublished Updated

CVE-2026-64170: Linux kernel · spi: qup: fix error pointer deref after DMA setup failure

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in d577c55d189e7ae150973058d13e299b6855633f : update Linux kernel when convenient.

Data as of 6 Nov 2026, 17:03 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in d577c55d189e7ae150973058d13e299b6855633f, a7e8f3efd50a165ba0189f6dc57f7e51a7d149db, 45760b72e84c1a1498f1a8a9047184c85299da20 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 612762e82ae6058d69b4ce734598491bf030afe7, < d577c55d189e7ae150973058d13e299b6855633f
Fixed in
  • d577c55d189e7ae150973058d13e299b6855633f
LinuxLinuxAffected
  • ≥ 612762e82ae6058d69b4ce734598491bf030afe7, < a7e8f3efd50a165ba0189f6dc57f7e51a7d149db
Fixed in
  • a7e8f3efd50a165ba0189f6dc57f7e51a7d149db
LinuxLinuxAffected
  • ≥ 612762e82ae6058d69b4ce734598491bf030afe7, < 45760b72e84c1a1498f1a8a9047184c85299da20
Fixed in
  • 45760b72e84c1a1498f1a8a9047184c85299da20
LinuxLinuxAffected
  • ≥ 612762e82ae6058d69b4ce734598491bf030afe7, < 9e673affb92c29d9ba879bf4ea81c5e840166b56
Fixed in
  • 9e673affb92c29d9ba879bf4ea81c5e840166b56
LinuxLinuxAffected
  • ≥ 612762e82ae6058d69b4ce734598491bf030afe7, < 8f9b61d255b1e989b8913b06c8ebe0aba5e1b238
Fixed in
  • 8f9b61d255b1e989b8913b06c8ebe0aba5e1b238
LinuxLinuxAffected
  • ≥ 612762e82ae6058d69b4ce734598491bf030afe7, < 4f4051e9d644c371c50de4a042b85bba6727d5c3
Fixed in
  • 4f4051e9d644c371c50de4a042b85bba6727d5c3

AI-suggested

A fix is available and has been applied in multiple Linux kernel commits. Users should update to a Linux kernel version that includes these fixes to remediate the issue.

Description

A vulnerability in the Linux kernel's SPI QUP driver could lead to dereferencing an error pointer after a DMA setup failure. The issue occurs because the driver does not clear DMA channel pointers on setup failure, which may cause invalid memory access during later probe errors or driver unbind. The driver falls back to PIO mode if DMA setup fails. This flaw has been fixed in several Linux kernel commits.

References

Community reviews

Loading reviews…