CVE-2026-64221

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-24. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

July 24, 2026

Last Modified

August 11, 2026

Advisory Details (8)

Auto-updated Jul 27, 2026
No patch confirmed yet.
generic

spi: ti-qspi: fix use-after-free after DMA setup failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f2dc841d7dc9063fe9b47ced869b1271e55052ae
generic

spi: ti-qspi: fix use-after-free after DMA setup failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ea6ec3343e05f7937a53eb6d7617b3abdb4abc19
generic

spi: ti-qspi: fix use-after-free after DMA setup failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d7a076fb596c7b408ed6df74793a597990a6d860
generic

spi: ti-qspi: fix use-after-free after DMA setup failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d6f422b122922d1abee907d673bcc990e5f3672d
generic

spi: ti-qspi: fix use-after-free after DMA setup failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9c6f306a8140962c7284197db54b96fdb5f468d6
generic

spi: ti-qspi: fix use-after-free after DMA setup failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3bbbe7ae3fdada0df4157c1ffe989f92dfa8dcd6
generic

spi: ti-qspi: fix use-after-free after DMA setup failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1cd927002120678bd5d23c760246639caa53040e
generic

spi: ti-qspi: fix use-after-free after DMA setup failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/178b9b570c0f75fa7e691490520328b20d19138e

Vendor Advisories for CVE-2026-64221(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-08-30ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-08-30ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-08-30ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-08-30ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(8)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 32× in last 7d / 169× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 199 total refreshes for this CVE.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-30 00:19 UTCEG score recompute
  3. 2026-08-30 00:19 UTCVendor advisory
  4. 2026-08-30 00:18 UTCGHSA enrichment
  5. 2026-08-28 21:42 UTCEPSS rescore
  6. 2026-08-27 21:21 UTCEG score recompute
  7. 2026-08-27 21:21 UTCVendor advisory
  8. 2026-08-27 21:21 UTCGHSA enrichment
  9. 2026-08-27 10:05 UTCVendor advisory
  10. 2026-08-27 10:04 UTCGHSA enrichment
  11. 2026-08-26 22:46 UTCEG score recompute
  12. 2026-08-26 22:46 UTCVendor advisory
  13. 2026-08-26 22:46 UTCGHSA enrichment
  14. 2026-08-26 14:47 UTCEPSS rescore
  15. 2026-08-26 11:30 UTCVendor advisory
  16. 2026-08-26 11:30 UTCGHSA enrichment
  17. 2026-08-25 23:45 UTCEG score recompute
  18. 2026-08-25 23:45 UTCVendor advisory
  19. 2026-08-25 23:45 UTCGHSA enrichment
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-25 12:29 UTCVendor advisory
  22. 2026-08-25 12:29 UTCGHSA enrichment
  23. 2026-08-25 01:00 UTCEG score recompute
  24. 2026-08-25 01:00 UTCGHSA enrichment
  25. 2026-08-24 13:44 UTCEG score recompute
Show 75 more
  1. 2026-08-24 13:44 UTCVendor advisory
  2. 2026-08-24 13:44 UTCGHSA enrichment
  3. 2026-08-24 02:28 UTCEG score recompute
  4. 2026-08-24 02:28 UTCVendor advisory
  5. 2026-08-24 02:28 UTCGHSA enrichment
  6. 2026-08-23 14:41 UTCVendor advisory
  7. 2026-08-23 14:41 UTCGHSA enrichment
  8. 2026-08-23 03:25 UTCEG score recompute
  9. 2026-08-23 03:25 UTCVendor advisory
  10. 2026-08-23 03:25 UTCGHSA enrichment
  11. 2026-08-23 00:19 UTCEPSS rescore
  12. 2026-08-22 16:09 UTCVendor advisory
  13. 2026-08-22 16:09 UTCGHSA enrichment
  14. 2026-08-22 04:48 UTCEG score recompute
  15. 2026-08-22 04:48 UTCVendor advisory
  16. 2026-08-22 04:48 UTCGHSA enrichment
  17. 2026-08-21 23:49 UTCEPSS rescore
  18. 2026-08-21 17:32 UTCVendor advisory
  19. 2026-08-21 17:32 UTCGHSA enrichment
  20. 2026-08-21 06:16 UTCEG score recompute
  21. 2026-08-21 06:16 UTCVendor advisory
  22. 2026-08-21 06:16 UTCGHSA enrichment
  23. 2026-08-20 22:55 UTCEPSS rescore
  24. 2026-08-20 18:59 UTCVendor advisory
  25. 2026-08-20 18:59 UTCGHSA enrichment
  26. 2026-08-20 07:43 UTCVendor advisory
  27. 2026-08-20 07:43 UTCGHSA enrichment
  28. 2026-08-19 20:27 UTCEG score recompute
  29. 2026-08-19 20:27 UTCVendor advisory
  30. 2026-08-19 20:27 UTCGHSA enrichment
  31. 2026-08-19 17:04 UTCEPSS rescore
  32. 2026-08-19 07:25 UTCVendor advisory
  33. 2026-08-19 07:24 UTCGHSA enrichment
  34. 2026-08-18 20:08 UTCGHSA enrichment
  35. 2026-08-18 08:50 UTCVendor advisory
  36. 2026-08-18 08:50 UTCGHSA enrichment
  37. 2026-08-17 21:08 UTCEG score recompute
  38. 2026-08-17 21:08 UTCVendor advisory
  39. 2026-08-17 21:08 UTCGHSA enrichment
  40. 2026-08-17 13:47 UTCEPSS rescore
  41. 2026-08-17 09:51 UTCVendor advisory
  42. 2026-08-17 09:51 UTCGHSA enrichment
  43. 2026-08-16 22:36 UTCEG score recompute
  44. 2026-08-16 22:36 UTCVendor advisory
  45. 2026-08-16 22:36 UTCGHSA enrichment
  46. 2026-08-16 14:56 UTCEPSS rescore
  47. 2026-08-16 11:19 UTCEG score recompute
  48. 2026-08-16 11:19 UTCVendor advisory
  49. 2026-08-16 11:19 UTCGHSA enrichment
  50. 2026-08-16 00:04 UTCVendor advisory
  51. 2026-08-16 00:04 UTCGHSA enrichment
  52. 2026-08-15 12:48 UTCVendor advisory
  53. 2026-08-15 12:48 UTCGHSA enrichment
  54. 2026-08-15 01:31 UTCEG score recompute
  55. 2026-08-15 01:31 UTCVendor advisory
  56. 2026-08-15 01:31 UTCGHSA enrichment
  57. 2026-08-15 01:30 UTCEPSS rescore
  58. 2026-08-14 14:15 UTCVendor advisory
  59. 2026-08-14 14:15 UTCGHSA enrichment
  60. 2026-08-14 02:59 UTCEG score recompute
  61. 2026-08-14 02:59 UTCVendor advisory
  62. 2026-08-14 02:59 UTCGHSA enrichment
  63. 2026-08-13 22:00 UTCEPSS rescore
  64. 2026-08-13 15:43 UTCGHSA enrichment
  65. 2026-08-13 04:27 UTCVendor advisory
  66. 2026-08-13 04:27 UTCGHSA enrichment
  67. 2026-08-12 17:12 UTCEG score recompute
  68. 2026-08-12 17:12 UTCVendor advisory
  69. 2026-08-12 17:12 UTCGHSA enrichment
  70. 2026-08-12 13:51 UTCEPSS rescore
  71. 2026-08-12 05:56 UTCVendor advisory
  72. 2026-08-12 05:56 UTCGHSA enrichment
  73. 2026-08-11 18:40 UTCEG score recompute
  74. 2026-08-11 18:40 UTCVendor advisory
  75. 2026-08-11 18:40 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-64221?
CVE-2026-64221 is a high vulnerability published on July 24, 2026. 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…
When was CVE-2026-64221 disclosed?
CVE-2026-64221 was first published in the National Vulnerability Database on July 24, 2026, with the most recent update on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64221 actively exploited?
CVE-2026-64221 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.4% of all scored CVEs.
What is the CVSS score of CVE-2026-64221?
CVE-2026-64221 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64221?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64221, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64221

Explore →

Is Your Infrastructure Affected by CVE-2026-64221?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs