CVE-2026-72142: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-63x6-874m-qjjg
Share
Published
Advisory Summary

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

CVE-2026-72142 at a Glance

CVE Identifier CVE-2026-72142
GHSA Identifier GHSA-63x6-874m-qjjg
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-72142

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-72142, 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: i2c: imx: fix locked bus on SMBus block-read of 0 (atomic) SMBus 3.1 6.5.7 allows a Block Read byte count of 0, but the atomic (polling) path rejects it as -EPROTO. Worse, it returns without a NACK+STOP: the next receive cycle has already started, so the target keeps holding SDA and the bus stays stuck until a power cycle for this i2c controller. Reading I2DR to obtain the count likewise arms the next byte on the count > I2C_SMBUS_BLOCK_MAX path, which also returned -EPROTO directly and left the bus held. Handle both: NACK the in-flight dummy byte (TXAK) and extend msgs->len so the existing last-byte handling emits STOP; the dummy byte is discarded. A count of 0 is a valid empty block read; a count above I2C_SMBUS_BLOCK_MAX is still reported as -EPROTO, but only after the bus has been released. The interrupt-driven path has the same flaw from a later commit and is fixed separately, as it carries a different Fixes: tag and stable range.

References

NVD — CVE-2026-72142 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-72142
git.kernel.org/stable/c/016ef0f6ca... WEB
https://git.kernel.org/stable/c/016ef0f6ca4bc9bf0330ac41bd2ea349759643e3
git.kernel.org/stable/c/0f29df3c3d... WEB
https://git.kernel.org/stable/c/0f29df3c3d607a9dbc14aed0e45504ced4d2e7ec
git.kernel.org/stable/c/38d4947431... WEB
https://git.kernel.org/stable/c/38d4947431b2410850409fda016b2ac9f640a4dd
git.kernel.org/stable/c/60ed00d466... WEB
https://git.kernel.org/stable/c/60ed00d46616a9232e42ea7a3e3c0273d7cf7543
git.kernel.org/stable/c/6d2c973926... WEB
https://git.kernel.org/stable/c/6d2c973926d0612360693bc559be2ffde836151b
git.kernel.org/stable/c/c882e8cc68... WEB
https://git.kernel.org/stable/c/c882e8cc68fb993700dc21fd6e754001e6297934
git.kernel.org/stable/c/cb2fc37857... WEB
https://git.kernel.org/stable/c/cb2fc37857693b55909fb77dc2c87cfbc1cdc476
git.kernel.org/stable/c/e3e8b02d47... WEB
https://git.kernel.org/stable/c/e3e8b02d4773cfc5ad561d2e5505efde36c6927a

Frequently Asked Questions

What is CVE-2026-72142?
CVE-2026-72142 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-72142?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-72142?
CVE-2026-72142 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-72142?
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-63x6-874m-qjjg",
  "modified" : "2026-08-23T15:32:59Z",
  "published" : "2026-08-15T06:32:13Z",
  "aliases" : [ "CVE-2026-72142" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ni2c: imx: fix locked bus on SMBus block-read of 0 (atomic)\n\nSMBus 3.1 6.5.7 allows a Block Read byte count of 0, but the atomic\n(polling) path rejects it as -EPROTO. Worse, it returns without a\nNACK+STOP: the next receive cycle has already started, so the target\nkeeps holding SDA and the bus stays stuck until a power cycle for\nthis i2c controller.\n\nReading I2DR to obtain the count likewise arms the next byte on the\ncount > I2C_SMBUS_BLOCK_MAX path, which also returned -EPROTO directly\nand left the bus held.\n\nHandle both: NACK the in-flight dummy byte (TXAK) and extend msgs->len so\nthe existing last-byte handling emits STOP; the dummy byte is discarded.\nA count of 0 is a valid empty block read; a count above\nI2C_SMBUS_BLOCK_MAX is still reported as -EPROTO, but only after the bus\nhas been released.\n\nThe interrupt-driven path has the same flaw from a later commit and is\nfixed separately, as it carries a different Fixes: tag and stable range.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-72142"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/016ef0f6ca4bc9bf0330ac41bd2ea349759643e3"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0f29df3c3d607a9dbc14aed0e45504ced4d2e7ec"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/38d4947431b2410850409fda016b2ac9f640a4dd"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/60ed00d46616a9232e42ea7a3e3c0273d7cf7543"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6d2c973926d0612360693bc559be2ffde836151b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c882e8cc68fb993700dc21fd6e754001e6297934"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/cb2fc37857693b55909fb77dc2c87cfbc1cdc476"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e3e8b02d4773cfc5ad561d2e5505efde36c6927a"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T06:21:31Z"
  }
}