CVE-2026-90342: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-xw74-j5c3-43ch
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-90342
GHSA Identifier GHSA-xw74-j5c3-43ch
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-90342

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-90342, 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: bpf: Fix mmap_lock deadlock on arena lock failure Reported by the Sashiko AI review. arena_vm_fault() returns VM_FAULT_RETRY when it can't take arena->spinlock, but it never took mmap_lock. The fault path assumes a VM_FAULT_RETRY handler already dropped mmap_lock and re-takes it on the retry, so mmap_lock gets taken twice and can deadlock: do_user_addr_fault() { fault = handle_mm_fault(...); // calls arena_vm_fault() if (fault & VM_FAULT_RETRY) goto retry; // re-locks mmap_lock mmap_read_unlock(mm); } Return VM_FAULT_SIGBUS instead, for two reasons: 1. We could keep VM_FAULT_RETRY, but then we'd have to drop the fault lock first and cap the retry ourselves, the way __folio_lock_or_retry() does. 2. A failed raw_res_spin_lock_irqsave() already means a possible deadlock was detected, so retrying just hits the same lock again. So returning VM_FAULT_RETRY here is overkill.

References

NVD — CVE-2026-90342 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-90342
git.kernel.org/stable/c/0b10b94547... WEB
https://git.kernel.org/stable/c/0b10b945479c954393d62ee3229d2f224a4ca91c
git.kernel.org/stable/c/af8087f167... WEB
https://git.kernel.org/stable/c/af8087f16714f7620c4db3e732baaa1b2337948f

Frequently Asked Questions

What is CVE-2026-90342?
CVE-2026-90342 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-90342?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-90342?
CVE-2026-90342 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-90342?
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-xw74-j5c3-43ch",
  "modified" : "2026-09-17T18:32:01Z",
  "published" : "2026-09-17T18:32:01Z",
  "aliases" : [ "CVE-2026-90342" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix mmap_lock deadlock on arena lock failure\n\nReported by the Sashiko AI review.\n\narena_vm_fault() returns VM_FAULT_RETRY when it can't take\narena->spinlock, but it never took mmap_lock. The fault path assumes a\nVM_FAULT_RETRY handler already dropped mmap_lock and re-takes it on the\nretry, so mmap_lock gets taken twice and can deadlock:\n\n\tdo_user_addr_fault()\n\t{\n\t\tfault = handle_mm_fault(...);   // calls arena_vm_fault()\n\t\tif (fault & VM_FAULT_RETRY)\n\t\t\tgoto retry;   // re-locks mmap_lock\n\t\tmmap_read_unlock(mm);\n\t}\n\nReturn VM_FAULT_SIGBUS instead, for two reasons:\n\n1. We could keep VM_FAULT_RETRY, but then we'd have to drop the fault\n   lock first and cap the retry ourselves, the way __folio_lock_or_retry()\n   does.\n\n2. A failed raw_res_spin_lock_irqsave() already means a possible deadlock\n   was detected, so retrying just hits the same lock again.\n\nSo returning VM_FAULT_RETRY here is overkill.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-90342"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0b10b945479c954393d62ee3229d2f224a4ca91c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/af8087f16714f7620c4db3e732baaa1b2337948f"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:17:32Z"
  }
}