# CVE-2026-64170 — Linux

> As of 2026-07-19, CVE-2026-64170 is a vulnerability in Linux, EPSS 0.1% (6.0th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-64170 as of 2026-07-19; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-07-19

## What is CVE-2026-64170?

In the Linux kernel, the following vulnerability has been resolved: spi: qup: fix error pointer deref after DMA setup failure The driver falls back to PIO mode if DMA setup fails during probe. Make sure to the clear the DMA channel pointers on setup failure to avoid dereferencing an error pointer (or attempting to release a channel a second time) on later probe errors or driver unbind. This issue was flagged by Sashiko when reviewing a devres allocation conversion patch.

1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 78 days ago.

## Severity and exploitation probability

- **EPSS (FIRST):** 0.1% probability of exploitation in the next 30 days, higher than 6.0% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 0.2/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-07-19

## Is CVE-2026-64170 being exploited?

It currently carries a trending score of 31 in the Threadlinqs vulnerability feed.

## Affected products and versions

- [Linux](https://intel.threadlinqs.com/vendors/linux): Linux

## How to fix CVE-2026-64170

No vendor patch reference has been recorded for CVE-2026-64170 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-64170

No threat campaign in the Threadlinqs corpus currently references CVE-2026-64170, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories. Last verified by Threadlinqs on 2026-07-21. This product uses the NVD API but is not endorsed or certified by the NVD.

**Other references**

- [git.kernel.org](https://git.kernel.org/stable/c/0bb3bd442f0bdad3932739a61dd6c580c9c1955e)
- [git.kernel.org (d577c55d189e7ae150973058d13e299b6855633f)](https://git.kernel.org/stable/c/d577c55d189e7ae150973058d13e299b6855633f)
- [git.kernel.org (9e673affb92c29d9ba879bf4ea81c5e840166b56)](https://git.kernel.org/stable/c/9e673affb92c29d9ba879bf4ea81c5e840166b56)
- [git.kernel.org (45760b72e84c1a1498f1a8a9047184c85299da20)](https://git.kernel.org/stable/c/45760b72e84c1a1498f1a8a9047184c85299da20)
- [git.kernel.org (8f9b61d255b1e989b8913b06c8ebe0aba5e1b238)](https://git.kernel.org/stable/c/8f9b61d255b1e989b8913b06c8ebe0aba5e1b238)

_Showing 5 of 8 recorded references._

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-64170
Full detection coverage and IOCs for threats exploiting CVE-2026-64170 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp