Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-64303, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.69% · top 46% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.

Affected products

  • Linux · Linux

    • affected 09c04466ce7ea494993c0635ba5edb6d2222a806 – < ad370d1c7a9a832f77b2341513cd31188c9443af
    • affected 09c04466ce7ea494993c0635ba5edb6d2222a806 – < cce2063404b2341e7b2bbf85eddfcd70a31a0033
    • affected 09c04466ce7ea494993c0635ba5edb6d2222a806 – < af39a2698f69b584d14a00cffe0f51a2caa15337
    • affected 09c04466ce7ea494993c0635ba5edb6d2222a806 – < e65505d91fa036a238968e4c10744244d1b968c4
    • affected 09c04466ce7ea494993c0635ba5edb6d2222a806 – < d5c1060218a3749c8a18b36f8169d910fce20639
    • affected 09c04466ce7ea494993c0635ba5edb6d2222a806 – < 808033d80d5c9f8adf7e8de9317389270ce13430
    • affected 09c04466ce7ea494993c0635ba5edb6d2222a806 – < 9d000bdd250d649a11cd7f733175686877344582
    • affected 09c04466ce7ea494993c0635ba5edb6d2222a806 – < 01980b5da56e573d62798d0ff6c86bcaa2b22cbe
  • Linux · Linux

    • affected 5.2
    • unaffected < 5.2
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.96 – ≤ 6.12.*
    • unaffected 6.18.39 – ≤ 6.18.*
    • unaffected 7.1.4 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-64303 badge
[![CVE-2026-64303](https://cveledger.app/badge/CVE-2026-64303.svg)](https://cveledger.app/cve/CVE-2026-64303)

Record last updated .