Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 39/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.69% (FIRST EPSS); higher than 53.1% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: Linux Linux 01980b5da56e573d62798d0ff6c86bcaa2b22cbe, 808033d80d5c9f8adf7e8de9317389270ce13430, 9d000bdd250d649a11cd7f733175686877344582; azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 6.6.145.2-1.

Low priority for now. Upgrade to Linux Linux 01980b5da56e573d62798d0ff6c86bcaa2b22cbe, 808033d80d5c9f8adf7e8de9317389270ce13430, 9d000bdd250d649a11cd7f733175686877344582; azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 6.6.145.2-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

CriticalCVSS 9.8 · v3.1—No exploit Fix available
Published
Jul 25, 2026
Updated
Oct 19, 2026
EPSS
0.6% · 53th percentile

Report tools

JSON

Action score

39

Monitor

Low priority for now.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.6%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
9.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-64303

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.2 and later · before 5.10.261
  • linux linux kernel5.11 and later · before 5.15.212
  • linux linux kernel5.16 and later · before 6.1.178
  • linux linux kernel6.2 and later · before 6.6.145
  • linux linux kernel6.7 and later · before 6.12.96
  • linux linux kernel6.13 and later · before 6.18.39
  • linux linux kernel6.19 and later · before 7.1.4

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.2affected
    • 09c04466ce7ea494993c0635ba5edb6d2222a806 and later · before ad370d1c7a9a832f77b2341513cd31188c9443afaffected · git
    • 09c04466ce7ea494993c0635ba5edb6d2222a806 and later · before cce2063404b2341e7b2bbf85eddfcd70a31a0033affected · git
    • 09c04466ce7ea494993c0635ba5edb6d2222a806 and later · before af39a2698f69b584d14a00cffe0f51a2caa15337affected · git
    • 09c04466ce7ea494993c0635ba5edb6d2222a806 and later · before e65505d91fa036a238968e4c10744244d1b968c4affected · git
    • 09c04466ce7ea494993c0635ba5edb6d2222a806 and later · before d5c1060218a3749c8a18b36f8169d910fce20639affected · git
    • 09c04466ce7ea494993c0635ba5edb6d2222a806 and later · before 808033d80d5c9f8adf7e8de9317389270ce13430affected · git
    • 09c04466ce7ea494993c0635ba5edb6d2222a806 and later · before 9d000bdd250d649a11cd7f733175686877344582affected · git
    • 09c04466ce7ea494993c0635ba5edb6d2222a806 and later · before 01980b5da56e573d62798d0ff6c86bcaa2b22cbeaffected · git
    • before 5.2not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:12linux-6.12before 6.12.100-1~deb12u16.12.100-1~deb12u1
Debian:13linuxbefore 6.12.96-16.12.96-1
Debian:14linuxbefore 7.1.4-17.1.4-1
Rocky Linux:9kernelbefore 0:5.14.0-687.64.1.el9_80:5.14.0-687.64.1.el9_8

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-64299Jul 25, 2026 · tracing: Prevent out-of-bounds read in glob matching
    28Monitor
  • ← EarlierCVE-2026-64301Jul 25, 2026 · regulator: scmi: fix of_node refcount leak in scmi_regulator_probe()
    22Monitor
  • Later →CVE-2026-64304Jul 25, 2026 · crypto: qat - validate RSA CRT component lengths
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux01980b5da56e573d62798d0ff6c86bcaa2b22cbeVendor (CNA)
Linux Linux808033d80d5c9f8adf7e8de9317389270ce13430Vendor (CNA)
Linux Linux9d000bdd250d649a11cd7f733175686877344582Vendor (CNA)
Linux Linuxad370d1c7a9a832f77b2341513cd31188c9443afVendor (CNA)
Linux Linuxaf39a2698f69b584d14a00cffe0f51a2caa15337Vendor (CNA)
Linux Linuxcce2063404b2341e7b2bbf85eddfcd70a31a0033Vendor (CNA)
Linux Linuxd5c1060218a3749c8a18b36f8169d910fce20639Vendor (CNA)
Linux Linuxe65505d91fa036a238968e4c10744244d1b968c4Vendor (CNA)
azl3 kernel 6.6.144.1-1 on Azure Linux 3.06.6.145.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.100-1~deb12u1 · Debian:12Package registry (OSV)
rocky linux:kernel0:5.14.0-687.64.1.el9_8 · Rocky Linux:9Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records