CVE-2026-90310: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-pg3g-fx7x-75v9
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-90310
GHSA Identifier GHSA-pg3g-fx7x-75v9
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-90310

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-90310, 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: xen/xenbus: check otherend_id only after it has been initialized When device just got initialized (for example on module load), the otherend_id field is initialized only after xenbus_read_otherend_details() gets called. If xenstore watch triggers xenbus_dev_changed() before that, it might consider still zeroed otherend_id field (not matching actual xenstore content) as a sign of device state reset. It can happen because xenstore watch are handled in another thread (xenwatch), which can run in parallel to the initial device probe running at module load. In that case, it would call device_unregister(), which would deadlock against device probe from module init. Fix this by considering dev->otherend_id change only after dev->otherend is set (which happen after otherend_id is initialized).

References

NVD — CVE-2026-90310 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-90310
git.kernel.org/stable/c/36fb592af3... WEB
https://git.kernel.org/stable/c/36fb592af353c55832e2cafe3fcfc3291be05f19
git.kernel.org/stable/c/c76cbf348c... WEB
https://git.kernel.org/stable/c/c76cbf348c7df077f93fa99a1225a527ce64cfa1

Frequently Asked Questions

What is CVE-2026-90310?
CVE-2026-90310 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-90310?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-90310?
CVE-2026-90310 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-90310?
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-pg3g-fx7x-75v9",
  "modified" : "2026-09-17T18:32:00Z",
  "published" : "2026-09-17T18:32:00Z",
  "aliases" : [ "CVE-2026-90310" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nxen/xenbus: check otherend_id only after it has been initialized\n\nWhen device just got initialized (for example on module load), the\notherend_id field is initialized only after\nxenbus_read_otherend_details() gets called. If xenstore watch triggers\nxenbus_dev_changed() before that, it might consider still zeroed\notherend_id field (not matching actual xenstore content) as a sign of\ndevice state reset. It can happen because xenstore watch are handled in\nanother thread (xenwatch), which can run in parallel to the initial\ndevice probe running at module load. In that case, it would call\ndevice_unregister(), which would deadlock against device probe from\nmodule init.\n\nFix this by considering dev->otherend_id change only after dev->otherend\nis set (which happen after otherend_id is initialized).",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-90310"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/36fb592af353c55832e2cafe3fcfc3291be05f19"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c76cbf348c7df077f93fa99a1225a527ce64cfa1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:17:28Z"
  }
}