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

> A use-after-free vulnerability in the Linux kernel's fsl-lpspi driver allows attackers to cause memory corruption or execute code via a specific DMA failure path.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jul 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-93644, BELL-CVE-2026-64303, DEBIAN-CVE-2026-64303, GHSA-8g65-pg22-jqr9, ROOT-OS-DEBIAN-12-CVE-2026-64303, ROOT-OS-UBUNTU-2204-CVE-2026-64303, UBUNTU-CVE-2026-64303

## What is CVE-2026-64303?

CVE-2026-64303 is a critical use after free vulnerability in Linux kernel, published on 25 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2026-64303?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-64303?

Apply the vendor's patch.

## Is CVE-2026-64303 being exploited?

There is no known exploitation of CVE-2026-64303 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-64303 and fix it if it is affected.

What it is: CVE-2026-64303 is a critical use after free vulnerability in Linux kernel, published on 25 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-64303 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-64303/ (Markdown: https://insights.sbomify.com/CVE-2026-64303/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-64303
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-64303
- OSV: https://osv.dev/vulnerability/CVE-2026-64303

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-64303/
Summaries are generated and may contain mistakes; the official description above is the record.