CVE-2026-93093: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-wj2w-288c-r9m4
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-93093
GHSA Identifier GHSA-wj2w-288c-r9m4
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-93093

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-93093, 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: Publish channel state before callbacks Transport setup can enable callbacks before the setup routine returns. mailbox_chan_setup() registers the mailbox client with mbox_request_channel(), and the mailbox controller startup path can enable interrupt delivery before SCMI mailbox channel state has been published. Similarly, smc_chan_setup() requests the optional A2P completion IRQ before the SMC transport has made its cinfo pointer visible. If a pending or spurious callback fires in those windows, the transport RX callback can dereference a NULL transport cinfo pointer. Publishing only the transport-private pointer is not sufficient either: an early callback can enter the SCMI core before scmi_chan_setup() has assigned cinfo->handle. The core derives scmi_info from cinfo->handle in the RX path, so a NULL handle can still fault even when the transport-private cinfo is valid. Assign cinfo->handle before invoking the transport setup callback. Publish the mailbox and SMC transport-private channel state before requesting the mailbox channels or IRQ, and clear the early-published pointers again on setup failure. Also unwind mailbox setup devres resources on failure so an optional RX setup error that is ignored by the core does not leave stale transport state behind.

References

NVD — CVE-2026-93093 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-93093
git.kernel.org/stable/c/0314900dcd... WEB
https://git.kernel.org/stable/c/0314900dcdde044af0208fed212035dbfaa55843
git.kernel.org/stable/c/1bea027f7e... WEB
https://git.kernel.org/stable/c/1bea027f7ef6fb889628b16c568a5f7c07a51b30
git.kernel.org/stable/c/6f3f532531... WEB
https://git.kernel.org/stable/c/6f3f532531e4a27d28a2240719d1b05ac11766c6
git.kernel.org/stable/c/a1bc587568... WEB
https://git.kernel.org/stable/c/a1bc587568a4e373db76261dc9561dfc3653917f

Frequently Asked Questions

What is CVE-2026-93093?
CVE-2026-93093 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-93093?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-93093?
CVE-2026-93093 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-93093?
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-wj2w-288c-r9m4",
  "modified" : "2026-09-17T18:32:09Z",
  "published" : "2026-09-17T18:32:09Z",
  "aliases" : [ "CVE-2026-93093" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nfirmware: arm_scmi: Publish channel state before callbacks\n\nTransport setup can enable callbacks before the setup routine returns.\nmailbox_chan_setup() registers the mailbox client with\nmbox_request_channel(), and the mailbox controller startup path can enable\ninterrupt delivery before SCMI mailbox channel state has been published.\nSimilarly, smc_chan_setup() requests the optional A2P completion IRQ before\nthe SMC transport has made its cinfo pointer visible.\n\nIf a pending or spurious callback fires in those windows, the transport RX\ncallback can dereference a NULL transport cinfo pointer. Publishing only\nthe transport-private pointer is not sufficient either: an early callback\ncan enter the SCMI core before scmi_chan_setup() has assigned\ncinfo->handle.\nThe core derives scmi_info from cinfo->handle in the RX path, so a NULL\nhandle can still fault even when the transport-private cinfo is valid.\n\nAssign cinfo->handle before invoking the transport setup callback. Publish\nthe mailbox and SMC transport-private channel state before requesting the\nmailbox channels or IRQ, and clear the early-published pointers again on\nsetup failure. Also unwind mailbox setup devres resources on failure so an\noptional RX setup error that is ignored by the core does not leave stale\ntransport state behind.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-93093"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0314900dcdde044af0208fed212035dbfaa55843"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1bea027f7ef6fb889628b16c568a5f7c07a51b30"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6f3f532531e4a27d28a2240719d1b05ac11766c6"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a1bc587568a4e373db76261dc9561dfc3653917f"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:18:03Z"
  }
}