CVE-2026-97994: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-h9m6-p5f9-c339
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-97994
GHSA Identifier GHSA-h9m6-p5f9-c339
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-97994

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-97994, 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: vhost/vdpa: reject VRING_NUM larger than device max vhost_vring_set_num() accepts any non-zero power-of-two queue size that fits in 16 bits. vhost-vdpa then passes that value to set_vq_num() without comparing it with get_vq_num_max(). A process with access to /dev/vhost-vdpa-* can therefore configure a queue larger than the device advertises. With vdpa_sim, the worker can walk descriptors beyond the mapped descriptor ring. KASAN reports a 16-byte out-of-bounds read, corresponding to one vring_desc, in the vringh IOTLB path: BUG: KASAN: out-of-bounds in _copy_from_iter Read of size 16 copy_from_iotlb copydesc_iotlb vringh_getdesc_iotlb vdpasim_net_work Cache get_vq_num_max() immediately after reset. Some backends derive it from writable queue-size state, so querying it after SET_NUM may return the current size instead of the device capability. Invalidate the cached value before reset so a failed reset leaves SET_NUM disabled. For VHOST_SET_VRING_NUM, copy the complete vring state once and use the same index and size for validation, vq->num, and set_vq_num(). This ensures that validation and use operate on the same copied values.

References

NVD — CVE-2026-97994 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-97994
git.kernel.org/stable/c/1d09201d81... WEB
https://git.kernel.org/stable/c/1d09201d81b7d3e276860cc7b7dbf6c6cbe8e9b4
git.kernel.org/stable/c/4875c65ca5... WEB
https://git.kernel.org/stable/c/4875c65ca53797a0a402fe2bb54d1b12f28b3cda
git.kernel.org/stable/c/59522639a7... WEB
https://git.kernel.org/stable/c/59522639a7d71cff4e20d594d0b9ea30dd0c77e0
git.kernel.org/stable/c/68232102f2... WEB
https://git.kernel.org/stable/c/68232102f20fc961327fb9e0f605a7eaadf030a9
git.kernel.org/stable/c/ccb1dc7c52... WEB
https://git.kernel.org/stable/c/ccb1dc7c527f8c925925cf92afc76ae590dac311

Frequently Asked Questions

What is CVE-2026-97994?
CVE-2026-97994 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-97994?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-97994?
CVE-2026-97994 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-97994?
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-h9m6-p5f9-c339",
  "modified" : "2026-10-03T12:31:24Z",
  "published" : "2026-09-25T12:31:32Z",
  "aliases" : [ "CVE-2026-97994" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nvhost/vdpa: reject VRING_NUM larger than device max\n\nvhost_vring_set_num() accepts any non-zero power-of-two queue size that\nfits in 16 bits. vhost-vdpa then passes that value to set_vq_num()\nwithout comparing it with get_vq_num_max().\n\nA process with access to /dev/vhost-vdpa-* can therefore configure a\nqueue larger than the device advertises. With vdpa_sim, the worker can\nwalk descriptors beyond the mapped descriptor ring. KASAN reports a\n16-byte out-of-bounds read, corresponding to one vring_desc, in the\nvringh IOTLB path:\n\n  BUG: KASAN: out-of-bounds in _copy_from_iter\n  Read of size 16\n  copy_from_iotlb\n  copydesc_iotlb\n  vringh_getdesc_iotlb\n  vdpasim_net_work\n\nCache get_vq_num_max() immediately after reset. Some backends derive\nit from writable queue-size state, so querying it after SET_NUM may\nreturn the current size instead of the device capability. Invalidate\nthe cached value before reset so a failed reset leaves SET_NUM\ndisabled.\n\nFor VHOST_SET_VRING_NUM, copy the complete vring state once and use\nthe same index and size for validation, vq->num, and set_vq_num().\nThis ensures that validation and use operate on the same copied values.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-97994"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1d09201d81b7d3e276860cc7b7dbf6c6cbe8e9b4"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/4875c65ca53797a0a402fe2bb54d1b12f28b3cda"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/59522639a7d71cff4e20d594d0b9ea30dd0c77e0"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/68232102f20fc961327fb9e0f605a7eaadf030a9"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ccb1dc7c527f8c925925cf92afc76ae590dac311"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-25T11:17:27Z"
  }
}