CVE-2026-72134: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-pv8g-5qg3-q63w
Share
CVSS 7.8
Published
Advisory Summary

CVE-2026-72134 is a HIGH (CVSS 7.8) security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-72134 at a Glance

CVE Identifier CVE-2026-72134
GHSA Identifier GHSA-pv8g-5qg3-q63w
Severity HIGH
CVSS v3.1 Base Score 7.8
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-72134

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-72134, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

References

NVD — CVE-2026-72134 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-72134
git.kernel.org/stable/c/245404c265... WEB
https://git.kernel.org/stable/c/245404c26563aafb36aafb01298f148db1851be3
git.kernel.org/stable/c/40dee2d3e9... WEB
https://git.kernel.org/stable/c/40dee2d3e9994aed9efe7bed40eb0e4d38d5a25c

Frequently Asked Questions

What is CVE-2026-72134?
CVE-2026-72134 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-72134?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-72134?
CVE-2026-72134 has a CVSS v3.1 base score of 7.8 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-72134?
CVE-2026-72134 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-72134?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-pv8g-5qg3-q63w",
  "modified" : "2026-08-17T06:33:12Z",
  "published" : "2026-08-15T06:32:13Z",
  "aliases" : [ "CVE-2026-72134" ],
  "details" : "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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-72134"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/245404c26563aafb36aafb01298f148db1851be3"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/40dee2d3e9994aed9efe7bed40eb0e4d38d5a25c"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T06:21:30Z"
  }
}