CVE-2026-93276: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-gfvh-9676-44ch
Published
Advisory Summary

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

CVE Identifier CVE-2026-93276
GHSA Identifier GHSA-gfvh-9676-44ch
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-93276

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-93276, 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: phy: renesas: phy-rcar-gen3-usb2: Fix devm action registration for disabled VBUS regulator devm_regulator_get_exclusive() initialises the regulator with enable_count = 1, requiring the consumer to disable it before release. The devm disable action was previously only registered when the caller explicitly requested enable, so when the regulator was left in its initial enabled state without an explicit enable call, the cleanup path skipped decrementing enable_count, triggering a WARN_ON during regulator release on device removal. Fix this by always registering the devm disable action based on the actual enabled state via regulator_is_enabled(), regardless of whether the caller requested an explicit enable. This covers both the explicitly enabled case and the initial state set by devm_regulator_get_exclusive().

References

Frequently Asked Questions

What is CVE-2026-93276?
CVE-2026-93276 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-93276?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-93276?
CVE-2026-93276 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-93276?
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-gfvh-9676-44ch",
  "modified" : "2026-09-24T18:31:25Z",
  "published" : "2026-09-24T18:31:25Z",
  "aliases" : [ "CVE-2026-93276" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nphy: renesas: phy-rcar-gen3-usb2: Fix devm action registration for disabled VBUS regulator\n\ndevm_regulator_get_exclusive() initialises the regulator with\nenable_count = 1, requiring the consumer to disable it before release.\n\nThe devm disable action was previously only registered when the caller\nexplicitly requested enable, so when the regulator was left in its initial\nenabled state without an explicit enable call, the cleanup path skipped\ndecrementing enable_count, triggering a WARN_ON during regulator\nrelease on device removal.\n\nFix this by always registering the devm disable action based on the actual\nenabled state via regulator_is_enabled(), regardless of whether the\ncaller requested an explicit enable. This covers both the explicitly\nenabled case and the initial state set by devm_regulator_get_exclusive().",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-93276"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/49c9b71b45081e5e5eeb507a2d6edb80d332dc59"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/935f6e837a83b86b073a7601f699dc2c00e01322"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/bf7fefbc26e292c08cfe7b6496b879109ef1475a"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-24T16:17:24Z"
  }
}