CVE-2026-72122: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-4cqx-6pr4-c34w
CVSS 7.3
Published
Advisory Summary

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

CVE-2026-72122 at a Glance

CVE Identifier CVE-2026-72122
GHSA Identifier GHSA-4cqx-6pr4-c34w
Severity HIGH
CVSS v3.1 Base Score 7.3
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.3

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:L).

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 Low (A:L)

How to Fix CVE-2026-72122

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-72122, 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: can: bcm: fix lockless bound/ifindex race and silent RX_SETUP failure bcm_sendmsg() reads bo->ifindex and checks bo->bound before taking lock_sock(), while bcm_notify(), bcm_connect() and bcm_release() all mutate both fields under that same lock. Because the lockless reads and the locked writes are unordered with respect to each other, a racing bcm_notify() (device unregister) or bcm_connect() (concurrent bind on another thread sharing the socket) can make bcm_sendmsg() observe an inconsistent combination, e.g. a stale bound=1 together with the now-cleared ifindex=0, silently turning a socket bound to a specific CAN interface into one that also matches "any" interface. Keep the lockless bo->bound check purely as a fast-path reject, and move the ifindex read (and a bo->bound re-check) into the locked section, where every writer already serializes. This removes the possibility of observing the two fields torn against each other, rather than trying to fix it with more READ_ONCE()/WRITE_ONCE() pairs on two independently updated fields. Annotate the now-purely-lockless bo->bound accesses consistently across all its write sites. Also fix bcm_rx_setup() silently returning success when the target device disappears concurrently instead of reporting -ENODEV, so a broken RX op is no longer left registered as if it had succeeded.

References

Frequently Asked Questions

What is CVE-2026-72122?
CVE-2026-72122 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-72122?
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-72122?
CVE-2026-72122 has a CVSS v3.1 base score of 7.3 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L.
What CWE is associated with CVE-2026-72122?
CVE-2026-72122 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-72122?
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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-4cqx-6pr4-c34w",
  "modified" : "2026-08-17T06:33:11Z",
  "published" : "2026-08-15T06:32:13Z",
  "aliases" : [ "CVE-2026-72122" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ncan: bcm: fix lockless bound/ifindex race and silent RX_SETUP failure\n\nbcm_sendmsg() reads bo->ifindex and checks bo->bound before taking\nlock_sock(), while bcm_notify(), bcm_connect() and bcm_release() all\nmutate both fields under that same lock. Because the lockless reads\nand the locked writes are unordered with respect to each other, a\nracing bcm_notify() (device unregister) or bcm_connect() (concurrent\nbind on another thread sharing the socket) can make bcm_sendmsg()\nobserve an inconsistent combination, e.g. a stale bound=1 together\nwith the now-cleared ifindex=0, silently turning a socket bound to a\nspecific CAN interface into one that also matches \"any\" interface.\n\nKeep the lockless bo->bound check purely as a fast-path reject, and\nmove the ifindex read (and a bo->bound re-check) into the locked\nsection, where every writer already serializes. This removes the\npossibility of observing the two fields torn against each other,\nrather than trying to fix it with more READ_ONCE()/WRITE_ONCE() pairs\non two independently updated fields. Annotate the now-purely-lockless\nbo->bound accesses consistently across all its write sites.\n\nAlso fix bcm_rx_setup() silently returning success when the target\ndevice disappears concurrently instead of reporting -ENODEV, so a\nbroken RX op is no longer left registered as if it had succeeded.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-72122"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0f6f9f95294b4cbb26ba02209e893e3bd91237c3"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/35f0ac19efb1a3f6c5e12c00e475a9ec2d9c3a6d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6bcc5cd247c2934373bc2a1cdf8bf12321169543"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9e60c586faeaed80d55ab8ce2a4b8e56133bc395"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b70f1a15533afeeec5d07f20bec3f3867ab1c7b6"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b9c6ac6fb4e01b34575816066e5d3890a57b3c86"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d9b091d9d22fee81ec53fb55d2032951993ceadb"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ffa80a2af27c97453861a5128e537214a31cd18a"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T06:21:29Z"
  }
}