In the Linux kernel, the following vulnerability has been resolved: spi: qup: fix error pointer deref after DMA setup failure The driver falls back… (CVE-2026-64170)
A vulnerability in the Linux kernel's spi qup driver was resolved that involved dereferencing an error pointer after a DMA setup failure. The driver falls back to PIO mode if DMA setup fails during probe, but previously did not clear DMA channel pointers on setup failure. This could lead to dereferencing invalid pointers or attempting to release a DMA channel multiple times during later probe errors or driver unbind. The issue was identified during a code review of a devres allocation patch.
AI Analysis
Technical Summary
The Linux kernel spi qup driver contained a flaw where, if DMA setup failed during device probe, the driver would fall back to PIO mode but fail to clear DMA channel pointers. This could cause the driver to dereference error pointers or attempt to release a DMA channel more than once during subsequent probe errors or driver unbind operations. The vulnerability was fixed by ensuring DMA channel pointers are cleared on setup failure, preventing invalid pointer dereferences and double release attempts.
Potential Impact
This vulnerability could cause kernel errors or crashes due to dereferencing invalid pointers or double releasing DMA channels during device probe or unbind operations. There is no indication of remote code execution or privilege escalation. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix for this vulnerability has been implemented in the Linux kernel. Users should update to a kernel version that includes this fix. Since this is not a cloud service, remediation requires applying the updated kernel. Patch status is not explicitly stated in the provided data; check the official Linux kernel advisories or vendor updates for the exact fixed versions and apply the official fix accordingly.
In the Linux kernel, the following vulnerability has been resolved: spi: qup: fix error pointer deref after DMA setup failure The driver falls back… (CVE-2026-64170)
Description
A vulnerability in the Linux kernel's spi qup driver was resolved that involved dereferencing an error pointer after a DMA setup failure. The driver falls back to PIO mode if DMA setup fails during probe, but previously did not clear DMA channel pointers on setup failure. This could lead to dereferencing invalid pointers or attempting to release a DMA channel multiple times during later probe errors or driver unbind. The issue was identified during a code review of a devres allocation patch.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel spi qup driver contained a flaw where, if DMA setup failed during device probe, the driver would fall back to PIO mode but fail to clear DMA channel pointers. This could cause the driver to dereference error pointers or attempt to release a DMA channel more than once during subsequent probe errors or driver unbind operations. The vulnerability was fixed by ensuring DMA channel pointers are cleared on setup failure, preventing invalid pointer dereferences and double release attempts.
Potential Impact
This vulnerability could cause kernel errors or crashes due to dereferencing invalid pointers or double releasing DMA channels during device probe or unbind operations. There is no indication of remote code execution or privilege escalation. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix for this vulnerability has been implemented in the Linux kernel. Users should update to a kernel version that includes this fix. Since this is not a cloud service, remediation requires applying the updated kernel. Patch status is not explicitly stated in the provided data; check the official Linux kernel advisories or vendor updates for the exact fixed versions and apply the official fix accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-m682-4gwr-mr4j
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64170"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27a82a4a8d598912a220
Added to database: 07/19/2026, 19:38:16 UTC
Last enriched: 07/19/2026, 19:40:02 UTC
Last updated: 07/20/2026, 15:18:41 UTC
Views: 14
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.