CVE-2026-72124: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-h95p-28wv-6wpp
Share
CVSS 8.8
Published
Advisory Summary

CVE-2026-72124 is a HIGH (CVSS 8.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-72124 at a Glance

CVE Identifier CVE-2026-72124
GHSA Identifier GHSA-h95p-28wv-6wpp
Severity HIGH
CVSS v3.1 Base Score 8.8
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 8.8

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

Attack Vector Adjacent (AV:A)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
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-72124

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-72124, 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: isotp: serialize TX state transitions under so->rx_lock The TX state machine (so->tx.state) is driven from three contexts: sendmsg() claiming and progressing a transfer, the RX path consuming Flow Control/echo frames, and two hrtimers timing out a stalled transfer. Mixing a lock-free cmpxchg() claim in sendmsg() with hrtimer_cancel() calls made under so->rx_lock elsewhere left windows where a frame or timer callback could act on a state that had already moved on, corrupting an unrelated transfer. so->rx_lock now covers the full lifecycle of a TX claim: sendmsg() takes it to check so->tx.state is ISOTP_IDLE, switch it to ISOTP_SENDING, bump so->tx_gen and drain the previous transfer's timers - all as one critical section. isotp_rcv_fc()/isotp_rcv_cf() already run under this lock via isotp_rcv(), and isotp_rcv_echo() now takes it itself, so none of them can ever observe a transfer mid-claim. This also means a transfer can no longer be handed to sendmsg()'s cleanup paths (signal or send error) while another thread is concurrently claiming or finishing it, so those paths can cancel timers and reset the state unconditionally. isotp_release() claims the socket the same way, so a racing sendmsg() sees a consistent ISOTP_SHUTDOWN and skips arming its timer or sending. Only the hrtimer callbacks stay outside so->rx_lock, since they run under so->rx_lock's cancellation elsewhere and taking it themselves would deadlock. so->tx_gen lets them recognize whether the transfer they timed out is still the one currently active, so they don't report an error against a transfer that has since completed or been superseded.

References

NVD — CVE-2026-72124 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-72124
git.kernel.org/stable/c/0b05eca958... WEB
https://git.kernel.org/stable/c/0b05eca9589f609e2491b528dccf683168a4cda8
git.kernel.org/stable/c/377a8f5007... WEB
https://git.kernel.org/stable/c/377a8f500704da42ed86a4541ed930e9dcfdb2ea
git.kernel.org/stable/c/37beb16e08... WEB
https://git.kernel.org/stable/c/37beb16e08cae94cc05840c7274225e3b0b38ae7
git.kernel.org/stable/c/4f1fdf1a1c... WEB
https://git.kernel.org/stable/c/4f1fdf1a1c317bcac0c6b6c8e12642c9983de1ca
git.kernel.org/stable/c/6da8119e8d... WEB
https://git.kernel.org/stable/c/6da8119e8dd542194103139812d1a4b7dcd1aedd
git.kernel.org/stable/c/a7d90e7b5e... WEB
https://git.kernel.org/stable/c/a7d90e7b5e75d7406c889fe36e9a61ee364a00cb
git.kernel.org/stable/c/bbedeb67a9... WEB
https://git.kernel.org/stable/c/bbedeb67a9a684f2fb78c55bd3662c400526715e
git.kernel.org/stable/c/cf070fe33b... WEB
https://git.kernel.org/stable/c/cf070fe33bfbd1a4c21236078fadb35dd223a157

Frequently Asked Questions

What is CVE-2026-72124?
CVE-2026-72124 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-72124?
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-72124?
CVE-2026-72124 has a CVSS v3.1 base score of 8.8 (HIGH) with vector string CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-72124?
CVE-2026-72124 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-72124?
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-h95p-28wv-6wpp",
  "modified" : "2026-08-19T18:32:27Z",
  "published" : "2026-08-15T06:32:12Z",
  "aliases" : [ "CVE-2026-72124" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ncan: isotp: serialize TX state transitions under so->rx_lock\n\nThe TX state machine (so->tx.state) is driven from three contexts:\nsendmsg() claiming and progressing a transfer, the RX path consuming\nFlow Control/echo frames, and two hrtimers timing out a stalled\ntransfer. Mixing a lock-free cmpxchg() claim in sendmsg() with\nhrtimer_cancel() calls made under so->rx_lock elsewhere left windows\nwhere a frame or timer callback could act on a state that had already\nmoved on, corrupting an unrelated transfer.\n\nso->rx_lock now covers the full lifecycle of a TX claim: sendmsg()\ntakes it to check so->tx.state is ISOTP_IDLE, switch it to\nISOTP_SENDING, bump so->tx_gen and drain the previous transfer's\ntimers - all as one critical section. isotp_rcv_fc()/isotp_rcv_cf()\nalready run under this lock via isotp_rcv(), and isotp_rcv_echo() now\ntakes it itself, so none of them can ever observe a transfer mid-claim.\nThis also means a transfer can no longer be handed to sendmsg()'s\ncleanup paths (signal or send error) while another thread is\nconcurrently claiming or finishing it, so those paths can cancel\ntimers and reset the state unconditionally.\n\nisotp_release() claims the socket the same way, so a racing sendmsg()\nsees a consistent ISOTP_SHUTDOWN and skips arming its timer or sending.\n\nOnly the hrtimer callbacks stay outside so->rx_lock, since they run\nunder so->rx_lock's cancellation elsewhere and taking it themselves\nwould deadlock. so->tx_gen lets them recognize whether the transfer\nthey timed out is still the one currently active, so they don't\nreport an error against a transfer that has since completed or been\nsuperseded.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-72124"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0b05eca9589f609e2491b528dccf683168a4cda8"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/377a8f500704da42ed86a4541ed930e9dcfdb2ea"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/37beb16e08cae94cc05840c7274225e3b0b38ae7"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/4f1fdf1a1c317bcac0c6b6c8e12642c9983de1ca"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6da8119e8dd542194103139812d1a4b7dcd1aedd"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a7d90e7b5e75d7406c889fe36e9a61ee364a00cb"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/bbedeb67a9a684f2fb78c55bd3662c400526715e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/cf070fe33bfbd1a4c21236078fadb35dd223a157"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T06:21:29Z"
  }
}