CVE-2026-64303: Linux kernel · Use After Free
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical · fixed in e65505d91fa036a238968e4c10744244d1b968c4 : patch Linux kernel as a priority.
Data as of 26 Oct 2026, 15:59 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers can reliably automate steps 1–4 of the kill chain
- Technical impact
- Total control over the software or total information disclosure
CISA SSVC assessment, 2026-10-16.
- Patch
- Available – fixed in e65505d91fa036a238968e4c10744244d1b968c4, d5c1060218a3749c8a18b36f8169d910fce20639, cce2063404b2341e7b2bbf85eddfcd70a31a0033 +5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 25 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
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.
References
- git.kernel.org/stable/c/ad370d1c7a9a832f77b2341513cd31188c9443af (opens in a new tab)
- git.kernel.org/stable/c/cce2063404b2341e7b2bbf85eddfcd70a31a0033 (opens in a new tab)
- git.kernel.org/stable/c/af39a2698f69b584d14a00cffe0f51a2caa15337 (opens in a new tab)
- git.kernel.org/stable/c/e65505d91fa036a238968e4c10744244d1b968c4 (opens in a new tab)
- git.kernel.org/stable/c/d5c1060218a3749c8a18b36f8169d910fce20639 (opens in a new tab)
- git.kernel.org/stable/c/808033d80d5c9f8adf7e8de9317389270ce13430 (opens in a new tab)
- git.kernel.org/stable/c/9d000bdd250d649a11cd7f733175686877344582 (opens in a new tab)
- git.kernel.org/stable/c/01980b5da56e573d62798d0ff6c86bcaa2b22cbe (opens in a new tab)