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-64221spi: ti-qspi: fix use-after-free after DMA setup failure

Description

In the Linux kernel, the following vulnerability has been resolved: spi: ti-qspi: fix use-after-free after DMA setup failure The driver falls back to PIO mode if DMA setup fails during probe. Make sure to clear the DMA channel pointer also if buffer allocation fails to avoid passing a pointer to the released channel to the DMA engine (or trying to free the channel a second time on late 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. · 5 days later

    Published

  3. · 12 days 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-64221, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Analyzed3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.13% · top 98% of all CVEs (13 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected c687c46e9e4527c4b4d82bc3cca58c1b08bcfb83 – < 9c6f306a8140962c7284197db54b96fdb5f468d6
    • affected c687c46e9e4527c4b4d82bc3cca58c1b08bcfb83 – < 3bbbe7ae3fdada0df4157c1ffe989f92dfa8dcd6
    • affected c687c46e9e4527c4b4d82bc3cca58c1b08bcfb83 – < d6f422b122922d1abee907d673bcc990e5f3672d
    • affected c687c46e9e4527c4b4d82bc3cca58c1b08bcfb83 – < f2dc841d7dc9063fe9b47ced869b1271e55052ae
    • affected c687c46e9e4527c4b4d82bc3cca58c1b08bcfb83 – < 1cd927002120678bd5d23c760246639caa53040e
    • affected c687c46e9e4527c4b4d82bc3cca58c1b08bcfb83 – < d7a076fb596c7b408ed6df74793a597990a6d860
    • affected c687c46e9e4527c4b4d82bc3cca58c1b08bcfb83 – < 178b9b570c0f75fa7e691490520328b20d19138e
    • affected c687c46e9e4527c4b4d82bc3cca58c1b08bcfb83 – < ea6ec3343e05f7937a53eb6d7617b3abdb4abc19
  • Linux · Linux

    • affected 4.12
    • unaffected < 4.12
    • unaffected 5.10.258 – ≤ 5.10.*
    • unaffected 5.15.209 – ≤ 5.15.*
    • unaffected 6.1.175 – ≤ 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-64221 badge
[![CVE-2026-64221](https://cveledger.app/badge/CVE-2026-64221.svg)](https://cveledger.app/cve/CVE-2026-64221)

Record last updated .