CVE-2026-90012: Software Security Vulnerability Vulnerability

CRITICAL
Advisory Identifier: GHSA-xm4q-v74w-px7x
Share
CVSS 9.8
Published
Advisory Summary

CVE-2026-90012 is a CRITICAL (CVSS 9.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-90012 at a Glance

CVE Identifier CVE-2026-90012
GHSA Identifier GHSA-xm4q-v74w-px7x
Severity CRITICAL
CVSS v3.1 Base Score 9.8
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 9.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
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-90012

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-90012, 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: spi: Fix DMA mapping ownership on partial map failure If RX mapping fails after TX mapping succeeds, __spi_map_msg() unmaps TX but leaves tx_sg_mapped set. If TX mapping fails on a later transfer, mappings created for earlier transfers remain active. In both cases, cur_{tx,rx}_dma_dev have not yet been updated because they are assigned only after every transfer has been mapped. The subsequent spi_unmap_msg() may therefore unmap the TX mapping again or release earlier mappings using a NULL or stale device. Using a NULL device can trigger an oops. An empty SG table does not prevent the NULL dereference because dma_unmap_sg_attrs() accesses the device before checking the entry count. Publish both mapping devices before mapping starts and unwind all failures through __spi_unmap_msg(). This clears the mapping flags and releases each mapping once with the device that created it. Publishing the devices before the loop also refreshes them when no transfer needs mapping. No mapping flag is set in that case, so current users do not use the pointers as mapping owners.

References

NVD — CVE-2026-90012 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-90012
git.kernel.org/stable/c/367cea239f... WEB
https://git.kernel.org/stable/c/367cea239fc93094e5c16a72724800e0358f5c46
git.kernel.org/stable/c/5def8b6aaa... WEB
https://git.kernel.org/stable/c/5def8b6aaad44603740786262b95b6f77df52a1c
git.kernel.org/stable/c/a38051fa2d... WEB
https://git.kernel.org/stable/c/a38051fa2ddedbc8ec15292c55e276880ec5b9a4
git.kernel.org/stable/c/cc8354213a... WEB
https://git.kernel.org/stable/c/cc8354213ad6bd5fb8cc05a3fa3701188d086626

Frequently Asked Questions

What is CVE-2026-90012?
CVE-2026-90012 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-90012?
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-90012?
CVE-2026-90012 has a CVSS v3.1 base score of 9.8 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-90012?
CVE-2026-90012 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-90012?
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-xm4q-v74w-px7x",
  "modified" : "2026-09-16T15:31:06Z",
  "published" : "2026-09-16T12:30:45Z",
  "aliases" : [ "CVE-2026-90012" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nspi: Fix DMA mapping ownership on partial map failure\n\nIf RX mapping fails after TX mapping succeeds, __spi_map_msg() unmaps\nTX but leaves tx_sg_mapped set. If TX mapping fails on a later\ntransfer, mappings created for earlier transfers remain active.\n\nIn both cases, cur_{tx,rx}_dma_dev have not yet been updated because they\nare assigned only after every transfer has been mapped. The subsequent\nspi_unmap_msg() may therefore unmap the TX mapping again or release\nearlier mappings using a NULL or stale device. Using a NULL device can\ntrigger an oops. An empty SG table does not prevent the NULL dereference\nbecause dma_unmap_sg_attrs() accesses the device before checking the\nentry count.\n\nPublish both mapping devices before mapping starts and unwind all\nfailures through __spi_unmap_msg(). This clears the mapping flags and\nreleases each mapping once with the device that created it.\n\nPublishing the devices before the loop also refreshes them when no\ntransfer needs mapping. No mapping flag is set in that case, so current\nusers do not use the pointers as mapping owners.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-90012"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/367cea239fc93094e5c16a72724800e0358f5c46"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5def8b6aaad44603740786262b95b6f77df52a1c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a38051fa2ddedbc8ec15292c55e276880ec5b9a4"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/cc8354213ad6bd5fb8cc05a3fa3701188d086626"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "CRITICAL",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-16T11:17:13Z"
  }
}