CVE-2026-64303

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

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

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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

spi: fsl-lpspi: terminate the RX channel on TX prepare failure path

When dmaengine_prep_slave_sg() fails for the TX channel, the error path terminates the TX DMA channel but leaves the RX channel running. Since the RX channel was already submitted and issued prior to preparing the TX descriptor, returning -EINVAL causes the SPI core to unmap the DMA buffers while the RX DMA engine continues writing to them, leading to potential memory corruption or use-after-free.

Terminate the RX channel before returning on the TX prepare failure path.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity98% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
50%
KEV
Not listed

Published

July 25, 2026

Last Modified

August 17, 2026

Advisory Details (8)

Auto-updated Aug 24, 2026
No patch confirmed yet.
generic

spi: fsl-lpspi: terminate the RX channel on TX prepare failure path - kernel/git/stable/linux.git - Linux kernel stable tree

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

spi: fsl-lpspi: terminate the RX channel on TX prepare failure path - kernel/git/stable/linux.git - Linux kernel stable tree

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

spi: fsl-lpspi: terminate the RX channel on TX prepare failure path - kernel/git/stable/linux.git - Linux kernel stable tree

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

spi: fsl-lpspi: terminate the RX channel on TX prepare failure path - kernel/git/stable/linux.git - Linux kernel stable tree

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

spi: fsl-lpspi: terminate the RX channel on TX prepare failure path - kernel/git/stable/linux.git - Linux kernel stable tree

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

spi: fsl-lpspi: terminate the RX channel on TX prepare failure path - kernel/git/stable/linux.git - Linux kernel stable tree

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

spi: fsl-lpspi: terminate the RX channel on TX prepare failure path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/808033d80d5c9f8adf7e8de9317389270ce13430
generic

spi: fsl-lpspi: terminate the RX channel on TX prepare failure path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/01980b5da56e573d62798d0ff6c86bcaa2b22cbe

Vendor Advisories for CVE-2026-64303(2)

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

Affected Packages

(6 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (55 versions)5.10.262-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.177-1~deb11u1 (22 versions)6.1.180-1~deb11u1—
Debian:12(2)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)6.1.180-1—
linux-6.12—6.12.100-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)6.12.96-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (156 versions)7.1.4-1—

Data Freshness Timeline

(refreshed 62× in last 7d / 306× 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 351 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64303?
CVE-2026-64303 is a critical vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: spi: fsl-lpspi: terminate the RX channel on TX prepare failure path When dmaengineprepslave_sg() fails for the TX channel, the error path terminates the TX DMA channel but leaves the RX channel running. Since the RX channel was…
When was CVE-2026-64303 disclosed?
CVE-2026-64303 was first published in the National Vulnerability Database on July 25, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64303 actively exploited?
CVE-2026-64303 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 50.0% of all scored CVEs.
What is the CVSS score of CVE-2026-64303?
CVE-2026-64303 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-64303?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64303, 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-64303

Explore →

Is Your Infrastructure Affected by CVE-2026-64303?

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

Start Free Scan →Browse All CVEs