CVE-2026-64303
Description
A flaw was found in the Linux kernel's fsl-lpspi driver. This vulnerability occurs when the transmit (TX) Direct Memory Access (DMA) channel fails to prepare, but the receive (RX) DMA channel continues to operate. This can lead to memory corruption or a use-after-free condition, potentially allowing an attacker to compromise system integrity or execute unauthorized code.
Statement
A flaw in the Linux kernel's fsl-lpspi SPI driver, rated IMPORTANT by Red Hat, affects the kernel and kernel-rt packages in Red Hat Enterprise Linux 9 and 10 as well as Red Hat In-Vehicle OS 2. When preparation of the transmit (TX) DMA descriptor fails, the driver's error path terminates only the TX DMA channel, while the already-submitted receive (RX) DMA channel keeps running. As a result, the SPI core unmaps the DMA buffers while the RX DMA engine continues writing to them, which can lead to memory corruption or a use-after-free and potentially compromise system integrity. Exploitation requires local access to a system using the NXP fsl-lpspi SPI controller, since the fault is reached only on the TX DMA prepare failure path. For this reason, Red Hat assessed a CVSS 3.1 score of 7.0 (AV:L/AC:H/PR:L) rather than the CVE.org score of 9.8, as the flaw does not expose a remote or unauthenticated attack vector. Red Hat Enterprise Linux 6, 7, and 8 are not affected because the vulnerable code is not present in those streams. A fix is being pursued for the affected Red Hat Enterprise Linux 9 and 10 and Red Hat In-Vehicle OS streams; in the RHEL 9.9 kernel stream a fix is not currently planned.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7 | N/A | 9.8 |
| Attack Vector | Local | N/A | Network |
| Attack Complexity | High | N/A | Low |
| Privileges Required | Low | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | High | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Memory
If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
