CVE-2026-72340: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-57m3-p558-ghpc
Share
CVSS 7.8
Published
Advisory Summary

CVE-2026-72340 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-72340 at a Glance

CVE Identifier CVE-2026-72340
GHSA Identifier GHSA-57m3-p558-ghpc
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-72340

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-72340, 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: net: microchip: vcap: fix races on the shared Super VCAP block The VCAP instances on a chip are not independent, yet they are locked independently. On sparx5 and lan969x the IS0 and IS2 instances are backed by the same Super VCAP hardware block and share its cache and command registers: every access drives the shared VCAP_SUPER_CTRL register and moves data through the shared cache registers. Accessing one instance therefore races with accessing another. The per-instance admin->lock cannot prevent this, as each instance takes a different lock. The locking issue is mostly disguised by the fact that the core usage of the vcap api runs under rtnl. However, the full rule dump in debugfs decodes rules straight from hardware (a READ command followed by a cache read) and runs outside rtnl, so it races a concurrent tc-flower rule write to another Super VCAP instance. Besides corrupting the dump, the read repopulates the shared cache between the writers cache fill and its write command, so the writer commits the wrong data and corrupts the hardware entry. Introduce vcap_lock() and vcap_unlock() helpers and route every rule lock site in the VCAP API and its debugfs code through them. Replace the per-instance admin->lock with a single mutex in struct vcap_control that serializes access to all instances. The helpers reach it through a new admin->vctrl back-pointer, and the clients initialise and destroy the control lock instead of a per-instance one. No path holds more than one instance lock, so collapsing them onto a single mutex cannot self-deadlock.

References

NVD — CVE-2026-72340 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-72340
git.kernel.org/stable/c/1e71a40d10... WEB
https://git.kernel.org/stable/c/1e71a40d101547380590db582213c1f1dce1f041
git.kernel.org/stable/c/49806bef95... WEB
https://git.kernel.org/stable/c/49806bef9572a2e012610517bc14ed0a4db0d1fc
git.kernel.org/stable/c/786456d0a2... WEB
https://git.kernel.org/stable/c/786456d0a244bbd405dfc60e4de51f8b348b9cb1
git.kernel.org/stable/c/952928564c... WEB
https://git.kernel.org/stable/c/952928564cc5fdb06f92d7e25c6cd2e1d816362b
git.kernel.org/stable/c/d7a8d500d7... WEB
https://git.kernel.org/stable/c/d7a8d500d7e42837bd8dce40cb52c97c6e8706a9

Frequently Asked Questions

What is CVE-2026-72340?
CVE-2026-72340 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-72340?
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-72340?
CVE-2026-72340 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-72340?
CVE-2026-72340 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-72340?
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-57m3-p558-ghpc",
  "modified" : "2026-08-17T06:33:24Z",
  "published" : "2026-08-15T06:32:21Z",
  "aliases" : [ "CVE-2026-72340" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: microchip: vcap: fix races on the shared Super VCAP block\n\nThe VCAP instances on a chip are not independent, yet they are locked\nindependently. On sparx5 and lan969x the IS0 and IS2 instances are\nbacked by the same Super VCAP hardware block and share its cache and\ncommand registers: every access drives the shared VCAP_SUPER_CTRL\nregister and moves data through the shared cache registers.\n\nAccessing one instance therefore races with accessing another. The\nper-instance admin->lock cannot prevent this, as each instance takes a\ndifferent lock.\n\nThe locking issue is mostly disguised by the fact that the core usage of\nthe vcap api runs under rtnl. However, the full rule dump in debugfs\ndecodes rules straight from hardware (a READ command followed by a cache\nread) and runs outside rtnl, so it races a concurrent tc-flower rule\nwrite to another Super VCAP instance.\n\nBesides corrupting the dump, the read repopulates the shared cache\nbetween the writers cache fill and its write command, so the writer\ncommits the wrong data and corrupts the hardware entry.\n\nIntroduce vcap_lock() and vcap_unlock() helpers and route every rule\nlock site in the VCAP API and its debugfs code through them. Replace the\nper-instance admin->lock with a single mutex in struct vcap_control that\nserializes access to all instances. The helpers reach it through a new\nadmin->vctrl back-pointer, and the clients initialise and destroy the\ncontrol lock instead of a per-instance one.\n\nNo path holds more than one instance lock, so collapsing them onto a\nsingle mutex cannot self-deadlock.",
  "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-72340"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1e71a40d101547380590db582213c1f1dce1f041"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/49806bef9572a2e012610517bc14ed0a4db0d1fc"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/786456d0a244bbd405dfc60e4de51f8b348b9cb1"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/952928564cc5fdb06f92d7e25c6cd2e1d816362b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d7a8d500d7e42837bd8dce40cb52c97c6e8706a9"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T06:22:07Z"
  }
}