CVE-2026-93080: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-mj5f-93r8-jjjp
Published
Advisory Summary

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

CVE Identifier CVE-2026-93080
GHSA Identifier GHSA-mj5f-93r8-jjjp
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-93080

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-93080, 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: Fix transport device teardown lookup SCMI transport devices are deliberately excluded from normal SCMI bus matching so protocol drivers cannot bind to the internal transport children. However, scmi_device_destroy() uses the same protocol/name lookup to find devices that must be unregistered during channel teardown. Split the match helper so driver matching still skips transport devices, while explicit child lookup can find them for teardown. Use a shared transport-device name prefix macro for both matching and name generation. Since transport-device names are derived from direction and protocol ID, reject duplicate protocol channel setup before creating or finding a transport device. This prevents malformed firmware with duplicate protocol child nodes from reusing an existing transport device and then destroying it when the duplicate IDR insertion fails.

References

Frequently Asked Questions

What is CVE-2026-93080?
CVE-2026-93080 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-93080?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-93080?
CVE-2026-93080 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-93080?
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-mj5f-93r8-jjjp",
  "modified" : "2026-09-17T18:32:09Z",
  "published" : "2026-09-17T18:32:09Z",
  "aliases" : [ "CVE-2026-93080" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nfirmware: arm_scmi: Fix transport device teardown lookup\n\nSCMI transport devices are deliberately excluded from normal SCMI bus\nmatching so protocol drivers cannot bind to the internal transport\nchildren. However, scmi_device_destroy() uses the same protocol/name\nlookup to find devices that must be unregistered during channel teardown.\n\nSplit the match helper so driver matching still skips transport devices,\nwhile explicit child lookup can find them for teardown. Use a shared\ntransport-device name prefix macro for both matching and name generation.\n\nSince transport-device names are derived from direction and protocol ID,\nreject duplicate protocol channel setup before creating or finding a\ntransport device. This prevents malformed firmware with duplicate\nprotocol child nodes from reusing an existing transport device and then\ndestroying it when the duplicate IDR insertion fails.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-93080"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/4635953b4c1af477e166073521a77de6279f6929"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a14dd8fe0a95db638c550ed984cfe2a7428c783d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c656427440ea627166394d00c4b72147d5d79c60"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:18:01Z"
  }
}