CVE-2026-93054: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-v69r-w76r-qv39
Share
CVSS 7.0
Published
Advisory Summary

CVE-2026-93054 is a HIGH (CVSS 7.0) security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-93054 at a Glance

CVE Identifier CVE-2026-93054
GHSA Identifier GHSA-v69r-w76r-qv39
Severity HIGH
CVSS v3.1 Base Score 7.0
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.0

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

Attack Vector Local (AV:L)
Attack Complexity High (AC:H)
Privileges Required Low (PR:L)
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-93054

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-93054, 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: uio: Fix stale info pointer in failed registration path After device_add(), the UIO device is visible to userspace and /dev/uioX can be opened. If a later setup step fails, __uio_register_device() unwinds the device but leaves idev->info pointing at the caller-owned struct uio_info. That is unsafe when an opener races with the failed registration path. The open file keeps a reference to the uio_device, while the caller sees registration failure and may free its struct uio_info. Later file operations can then follow idev->info and dereference freed memory. Handle post-device_add() failures like unregister: remove UIO attributes while the info pointer is still valid, then clear idev->info under info_lock and wake existing waiters/async users before removing the device and minor. This makes already-open file descriptors observe the same "device gone" state as normal uio_unregister_device().

References

NVD — CVE-2026-93054 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-93054
git.kernel.org/stable/c/15340b00e6... WEB
https://git.kernel.org/stable/c/15340b00e665af805523b08515294a1aa1778151
git.kernel.org/stable/c/16695e9059... WEB
https://git.kernel.org/stable/c/16695e9059d80ea6661e8399064b0c01f641dd8c
git.kernel.org/stable/c/234156f6c6... WEB
https://git.kernel.org/stable/c/234156f6c6d9ec35dc47abbcc3adc3c79fc6a5ac
git.kernel.org/stable/c/506b43dde5... WEB
https://git.kernel.org/stable/c/506b43dde5f9ac0068b1360e6b5dbee07fda59fb
git.kernel.org/stable/c/63eaa76633... WEB
https://git.kernel.org/stable/c/63eaa7663335d482a8825c231213e312cacea567
git.kernel.org/stable/c/67b6fc084b... WEB
https://git.kernel.org/stable/c/67b6fc084b034a91c3ec7907a3fed89a2450f30b
git.kernel.org/stable/c/df4faf6519... WEB
https://git.kernel.org/stable/c/df4faf65194ec6c315a59be4c6749eaeb3009243
git.kernel.org/stable/c/ec5bd67311... WEB
https://git.kernel.org/stable/c/ec5bd6731183eb6f619140c9bef2ee11ed818c20

Frequently Asked Questions

What is CVE-2026-93054?
CVE-2026-93054 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-93054?
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-93054?
CVE-2026-93054 has a CVSS v3.1 base score of 7.0 (HIGH) with vector string CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-93054?
CVE-2026-93054 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-93054?
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-v69r-w76r-qv39",
  "modified" : "2026-09-18T18:31:33Z",
  "published" : "2026-09-17T18:32:08Z",
  "aliases" : [ "CVE-2026-93054" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nuio: Fix stale info pointer in failed registration path\n\nAfter device_add(), the UIO device is visible to userspace and /dev/uioX\ncan be opened. If a later setup step fails, __uio_register_device()\nunwinds the device but leaves idev->info pointing at the caller-owned\nstruct uio_info.\n\nThat is unsafe when an opener races with the failed registration path.\nThe open file keeps a reference to the uio_device, while the caller sees\nregistration failure and may free its struct uio_info. Later file\noperations can then follow idev->info and dereference freed memory.\n\nHandle post-device_add() failures like unregister: remove UIO attributes\nwhile the info pointer is still valid, then clear idev->info under\ninfo_lock and wake existing waiters/async users before removing the\ndevice and minor. This makes already-open file descriptors observe the\nsame \"device gone\" state as normal uio_unregister_device().",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-93054"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/15340b00e665af805523b08515294a1aa1778151"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/16695e9059d80ea6661e8399064b0c01f641dd8c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/234156f6c6d9ec35dc47abbcc3adc3c79fc6a5ac"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/506b43dde5f9ac0068b1360e6b5dbee07fda59fb"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/63eaa7663335d482a8825c231213e312cacea567"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/67b6fc084b034a91c3ec7907a3fed89a2450f30b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/df4faf65194ec6c315a59be4c6749eaeb3009243"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ec5bd6731183eb6f619140c9bef2ee11ed818c20"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:17:58Z"
  }
}