Kernel-level Linux vulnerability with CVSS 9.8 impacting core OS used broadly; can enable kernel compromise or outages and requires org-wide attention.
CVE-2026-64303
Linux fsl-lpspi DMA bug can cause kernel memory corruption/use-after-free.
Is CVE-2026-64303 being exploited?
Not confirmed. CVE-2026-64303 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.69% probability of exploitation in the next 30 days.
How severe is CVE-2026-64303?
CVE-2026-64303 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-64303?
Yes. A fix has been recorded for CVE-2026-64303. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64303 affect?
CVE-2026-64303 affects Linux kernel (fsl-lpspi driver), Embedded SoCs using NXP/Freescale LPSPI, Linux distributions shipping affected kernels. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64303?
Apply vendor/mainline kernel patch or backport immediately and reboot affected systems.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
RX DMA left running after TX prepare failure causes kernel use-after-free/memory corruption, enabling local privilege escalation, arbitrary kernel code execution or DoS.
Immediate action required
- affected>= 09c04466ce7ea494993c0635ba5edb6d2222a806 and < ad370d1c7a9a832f77b2341513cd31188c9443af
- affected>= 09c04466ce7ea494993c0635ba5edb6d2222a806 and < cce2063404b2341e7b2bbf85eddfcd70a31a0033
- affected>= 09c04466ce7ea494993c0635ba5edb6d2222a806 and < af39a2698f69b584d14a00cffe0f51a2caa15337
- affected>= 09c04466ce7ea494993c0635ba5edb6d2222a806 and < e65505d91fa036a238968e4c10744244d1b968c4
- affected>= 09c04466ce7ea494993c0635ba5edb6d2222a806 and < d5c1060218a3749c8a18b36f8169d910fce20639
- affected>= 09c04466ce7ea494993c0635ba5edb6d2222a806 and < 808033d80d5c9f8adf7e8de9317389270ce13430
- affected>= 09c04466ce7ea494993c0635ba5edb6d2222a806 and < 9d000bdd250d649a11cd7f733175686877344582
- affected>= 09c04466ce7ea494993c0635ba5edb6d2222a806 and < 01980b5da56e573d62798d0ff6c86bcaa2b22cbe
- affected5.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.