CVE-2026-72134
Received Received - Intake

SPI Controller Misconfiguration Leads to Data Corruption in Linux Kernel

Vulnerability report for CVE-2026-72134, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-15

Last updated on: 2026-08-17

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: spi: imx: reconfigure for PIO when DMA cannot be started When spi_imx_can_dma() selects DMA, the ECSPI is configured for DMA: spi_imx_setupxfer() sets CTRL.SMC and clears dynamic_burst, and spi_imx_dma_transfer() programs the dynamic-burst BURST_LENGTH and the SDMA watermarks. If the DMA descriptor cannot be prepared (dmaengine_prep_slave_single() returns NULL), the transfer is failed with SPI_TRANS_FAIL_NO_START and falls back to PIO. The dynamic-burst DMA path uses its own bounce buffers instead of the SPI core's mapping, so xfer->{tx,rx}_sg_mapped are not set and the core's DMA->PIO retry is skipped; the driver falls back to PIO internally. But none of the DMA-mode configuration is undone, so the PIO transfer runs with CTRL.SMC set, the wrong burst length and dynamic_burst cleared, and the transferred data is corrupted. This is easily hit on i.MX8MP boards that describe ECSPI DMA in the device tree but run SDMA on ROM firmware (no external sdma-imx7d.bin): every ECSPI DMA prepare fails. An Infineon SLB9670 TPM on ECSPI1 then returns shifted TPM2_GetCapability data, is flagged "field failure mode", /dev/tpmrm0 is never created. Set controller->fallback before re-running spi_imx_setupxfer() so the ECSPI is reconfigured exactly like a normal PIO transfer. With controller->fallback set, spi_imx_setupxfer() sees spi_imx_can_dma() return false, so it clears spi_imx->usedma and reprograms the controller (clears CTRL.SMC, restores dynamic_burst and the PIO burst length). No explicit spi_imx->usedma = false is needed: setupxfer() already updates it from the can_dma() result.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-15
Last Modified
2026-08-17
Generated
2026-09-04
AI Q&A
2026-08-15
EPSS Evaluated
2026-09-03
NVD
EUVD

Affected Vendors & Products

Currently, no data is known.

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel affects the SPI (Serial Peripheral Interface) driver for i.MX devices. When DMA (Direct Memory Access) is selected for SPI transfers but fails to initialize, the system attempts to fall back to PIO (Programmed Input/Output). However, the driver does not properly reset the DMA configuration settings, causing the PIO transfer to use incorrect parameters. This results in corrupted data being transferred.

Detection Guidance

This vulnerability affects the Linux kernel's SPI driver for i.MX devices. Detection involves checking if the system uses affected SPI controllers (ECSPI) with DMA enabled but failing to initialize properly. Look for corrupted data transfers or missing device nodes like /dev/tpmrm0 on i.MX8MP boards. Check kernel logs for SPI transfer failures or DMA errors.

Impact Analysis

If you use an i.MX8MP board with an Infineon SLB9670 TPM connected via ECSPI, this vulnerability could cause the TPM to return incorrect data. This may lead to security issues, such as authentication failures or misidentification of the TPM's status. The system may also fail to create the /dev/tpmrm0 device, preventing proper TPM functionality.

Compliance Impact

This vulnerability affects compliance with standards and regulations like GDPR and HIPAA by potentially causing data corruption during SPI transfers, which could lead to incorrect data handling or security failures in systems processing sensitive information.

Mitigation Strategies

Apply the kernel patch that sets controller->fallback before re-running spi_imx_setupxfer(). This ensures proper PIO fallback configuration. Update to a fixed kernel version. If using i.MX8MP with ECSPI, verify SDMA firmware is properly loaded or disable DMA for ECSPI in device tree.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-72134. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart