CVE-2026-93084: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-mw9p-h9xr-r672
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-93084
GHSA Identifier GHSA-mw9p-h9xr-r672
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-93084

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-93084, 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: firmware: arm_scmi: Drop handle on protocol bind failures The SCMI bus notifier acquires an SCMI handle when the driver core emits BUS_NOTIFY_BIND_DRIVER, before invoking the protocol driver probe callback. The protocol probe path only checks whether sdev->handle is set. If device_link_add() fails after the handle has been acquired, the protocol device can still bind with a valid handle but without the dependency link to the SCMI parent. A concurrent parent unbind can then miss the child and tear down the SCMI instance while the child still holds a handle into it. If the protocol driver probe later fails, for example with -EPROBE_DEFER, the driver core emits BUS_NOTIFY_DRIVER_NOT_BOUND rather than BUS_NOTIFY_UNBOUND_DRIVER. The SCMI notifier only released the handle on BUS_NOTIFY_UNBOUND_DRIVER, so each failed protocol-device bind leaked the SCMI instance users refcount and left sdev->handle set after the failed probe. Make the link helper report failure and drop the acquired handle if the link cannot be created. Also handle BUS_NOTIFY_DRIVER_NOT_BOUND in the same cleanup path used for unbind so failed probes balance the earlier BUS_NOTIFY_BIND_DRIVER acquisition.

References

NVD — CVE-2026-93084 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-93084
git.kernel.org/stable/c/0f860db24e... WEB
https://git.kernel.org/stable/c/0f860db24ee95e5da4866303a35e55098b9641b3
git.kernel.org/stable/c/77d2985d1e... WEB
https://git.kernel.org/stable/c/77d2985d1e80e67f32026fc03e975c4c83cc543d
git.kernel.org/stable/c/a54dc23e8b... WEB
https://git.kernel.org/stable/c/a54dc23e8bd2246c28eafffa60b4634f0d1a11cc
git.kernel.org/stable/c/df273eced7... WEB
https://git.kernel.org/stable/c/df273eced7cec550465fd1bb82a5d2c3c7d3c437
git.kernel.org/stable/c/e3a5c30d23... WEB
https://git.kernel.org/stable/c/e3a5c30d233ca5d3e799a80da806554c703bda13

Frequently Asked Questions

What is CVE-2026-93084?
CVE-2026-93084 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-93084?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-93084?
CVE-2026-93084 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-93084?
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-mw9p-h9xr-r672",
  "modified" : "2026-09-17T18:32:09Z",
  "published" : "2026-09-17T18:32:09Z",
  "aliases" : [ "CVE-2026-93084" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nfirmware: arm_scmi: Drop handle on protocol bind failures\n\nThe SCMI bus notifier acquires an SCMI handle when the driver core emits\nBUS_NOTIFY_BIND_DRIVER, before invoking the protocol driver probe\ncallback. The protocol probe path only checks whether sdev->handle is\nset.\n\nIf device_link_add() fails after the handle has been acquired, the\nprotocol device can still bind with a valid handle but without the\ndependency link to the SCMI parent. A concurrent parent unbind can then\nmiss the child and tear down the SCMI instance while the child still\nholds a handle into it.\n\nIf the protocol driver probe later fails, for example with\n-EPROBE_DEFER, the driver core emits BUS_NOTIFY_DRIVER_NOT_BOUND rather\nthan BUS_NOTIFY_UNBOUND_DRIVER. The SCMI notifier only released the\nhandle on BUS_NOTIFY_UNBOUND_DRIVER, so each failed protocol-device bind\nleaked the SCMI instance users refcount and left sdev->handle set after\nthe failed probe.\n\nMake the link helper report failure and drop the acquired handle if the\nlink cannot be created. Also handle BUS_NOTIFY_DRIVER_NOT_BOUND in the\nsame cleanup path used for unbind so failed probes balance the earlier\nBUS_NOTIFY_BIND_DRIVER acquisition.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-93084"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0f860db24ee95e5da4866303a35e55098b9641b3"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/77d2985d1e80e67f32026fc03e975c4c83cc543d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a54dc23e8bd2246c28eafffa60b4634f0d1a11cc"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/df273eced7cec550465fd1bb82a5d2c3c7d3c437"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e3a5c30d233ca5d3e799a80da806554c703bda13"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:18:02Z"
  }
}