Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 4 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-64170, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.11% · top 98% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 612762e82ae6058d69b4ce734598491bf030afe7 – < 0bb3bd442f0bdad3932739a61dd6c580c9c1955e
    • affected 612762e82ae6058d69b4ce734598491bf030afe7 – < d577c55d189e7ae150973058d13e299b6855633f
    • affected 612762e82ae6058d69b4ce734598491bf030afe7 – < 9e673affb92c29d9ba879bf4ea81c5e840166b56
    • affected 612762e82ae6058d69b4ce734598491bf030afe7 – < 45760b72e84c1a1498f1a8a9047184c85299da20
    • affected 612762e82ae6058d69b4ce734598491bf030afe7 – < 8f9b61d255b1e989b8913b06c8ebe0aba5e1b238
    • affected 612762e82ae6058d69b4ce734598491bf030afe7 – < 4bb4764f2c51f03f657a28029eb0595d8223aab5
    • affected 612762e82ae6058d69b4ce734598491bf030afe7 – < 4f4051e9d644c371c50de4a042b85bba6727d5c3
    • affected 612762e82ae6058d69b4ce734598491bf030afe7 – < a7e8f3efd50a165ba0189f6dc57f7e51a7d149db
  • Linux · Linux

    • affected 4.1
    • unaffected < 4.1
    • unaffected 5.10.259 – ≤ 5.10.*
    • unaffected 5.15.210 – ≤ 5.15.*
    • unaffected 6.1.176 – ≤ 6.1.*
    • unaffected 6.6.142 – ≤ 6.6.*
    • unaffected 6.12.92 – ≤ 6.12.*
    • unaffected 6.18.34 – ≤ 6.18.*
    • unaffected 7.0.11 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-64170 badge
[![CVE-2026-64170](https://cveledger.app/badge/CVE-2026-64170.svg)](https://cveledger.app/cve/CVE-2026-64170)

Record last updated .