« Volver al listado

CVE-2026-72134

Estado: RecibidaAlta (7.8)—

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.

Leer descripción completaMostrar menos

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

Probabilidad de explotación (EPSS)

EPSS (Exploit Prediction Scoring System, de FIRST) estima la probabilidad de que una vulnerabilidad sea explotada en 30 días. Complementa a CVSS (impacto) y a CISA KEV (explotación confirmada).

🎯 Técnicas ATT&CK

Cómo se explota esta vulnerabilidad y qué consigue el atacante, en el lenguaje de MITRE ATT&CK.

Vulnerabilidad local (AV:L/PR:L) sin interacción que corrompe datos en transferencias SPI por fallo en reconfiguración; impacto principal es manipulación de datos (ECSPI reconfigura incorrectamente), secundario es negación de servicio (dispositivo TPM no inicializado).

Inferido por nuestro agente de análisis a partir de la descripción oficial, el vector CVSS y la CWE, y comprobado por un supervisor. Puede contener errores.

🛡️ Mitigaciones ATT&CK que cubren estas técnicas

Threat Intelligence ProgramRestrict File and Directory PermissionsRemote Data StorageFilter Network TrafficExecution PreventionEncrypt Sensitive Information

Tecnologías afectadas (1)

⚠ Inferidas por IA a partir de la descripción — NVD aún no ha analizado esta CVE; no son CPE verificados.

Linux — Linux KernelAI

Referencias

JSON original (NVD)

Mostrar
{
  "id": "CVE-2026-72134",
  "cveTags": [],
  "metrics": {
    "cvssMetricV31": [
      {
        "type": "Secondary",
        "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "cvssData": {
          "scope": "UNCHANGED",
          "version": "3.1",
          "baseScore": 7.8,
          "attackVector": "LOCAL",
          "baseSeverity": "HIGH",
          "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
          "integrityImpact": "HIGH",
          "userInteraction": "NONE",
          "attackComplexity": "LOW",
          "availabilityImpact": "HIGH",
          "privilegesRequired": "LOW",
          "confidentialityImpact": "HIGH"
        },
        "impactScore": 5.9,
        "exploitabilityScore": 1.8
      }
    ]
  },
  "affected": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "affectedData": [
        {
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "product": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "faa8e404ad8e686cb98c51dc507fdcacfb8020ce",
              "lessThan": "40dee2d3e9994aed9efe7bed40eb0e4d38d5a25c",
              "versionType": "git"
            },
            {
              "status": "affected",
              "version": "faa8e404ad8e686cb98c51dc507fdcacfb8020ce",
              "lessThan": "245404c26563aafb36aafb01298f148db1851be3",
              "versionType": "git"
            }
          ],
          "programFiles": [
            "drivers/spi/spi-imx.c"
          ],
          "defaultStatus": "unaffected"
        },
        {
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "product": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "7.0"
            },
            {
              "status": "unaffected",
              "version": "0",
              "lessThan": "7.0",
              "versionType": "semver"
            },
            {
              "status": "unaffected",
              "version": "7.1.5",
              "versionType": "semver",
              "lessThanOrEqual": "7.1.*"
            },
            {
              "status": "unaffected",
              "version": "7.2",
              "versionType": "original_commit_for_fix",
              "lessThanOrEqual": "*"
            }
          ],
          "programFiles": [
            "drivers/spi/spi-imx.c"
          ],
          "defaultStatus": "affected"
        }
      ]
    }
  ],
  "published": "2026-08-15T06:21:30.880",
  "references": [
    {
      "url": "https://git.kernel.org/stable/c/245404c26563aafb36aafb01298f148db1851be3",
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    },
    {
      "url": "https://git.kernel.org/stable/c/40dee2d3e9994aed9efe7bed40eb0e4d38d5a25c",
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    }
  ],
  "vulnStatus": "Received",
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nspi: imx: reconfigure for PIO when DMA cannot be started\n\nWhen spi_imx_can_dma() selects DMA, the ECSPI is configured for DMA:\nspi_imx_setupxfer() sets CTRL.SMC and clears dynamic_burst, and\nspi_imx_dma_transfer() programs the dynamic-burst BURST_LENGTH and the\nSDMA watermarks.\n\nIf the DMA descriptor cannot be prepared (dmaengine_prep_slave_single()\nreturns NULL), the transfer is failed with SPI_TRANS_FAIL_NO_START and\nfalls back to PIO. The dynamic-burst DMA path uses its own bounce\nbuffers instead of the SPI core's mapping, so xfer->{tx,rx}_sg_mapped\nare not set and the core's DMA->PIO retry is skipped; the driver falls\nback to PIO internally. But none of the DMA-mode configuration is\nundone, so the PIO transfer runs with CTRL.SMC set, the wrong burst\nlength and dynamic_burst cleared, and the transferred data is corrupted.\n\nThis is easily hit on i.MX8MP boards that describe ECSPI DMA in the\ndevice tree but run SDMA on ROM firmware (no external sdma-imx7d.bin):\nevery ECSPI DMA prepare fails. An Infineon SLB9670 TPM on ECSPI1 then\nreturns shifted TPM2_GetCapability data, is flagged \"field failure\nmode\", /dev/tpmrm0 is never created.\n\nSet controller->fallback before re-running spi_imx_setupxfer() so the\nECSPI is reconfigured exactly like a normal PIO transfer. With\ncontroller->fallback set, spi_imx_setupxfer() sees spi_imx_can_dma()\nreturn false, so it clears spi_imx->usedma and reprograms the controller\n(clears CTRL.SMC, restores dynamic_burst and the PIO burst length). No\nexplicit spi_imx->usedma = false is needed: setupxfer() already updates\nit from the can_dma() result."
    }
  ],
  "lastModified": "2026-08-17T06:18:13.150",
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}