CVE-2026-97900: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-fx27-pfff-j2g5
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-97900
GHSA Identifier GHSA-fx27-pfff-j2g5
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-97900

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-97900, 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: drm/drm_exec: fix up contended obj when num_objects is 0 drm_exec_prepare_array() silently returns success without calling drm_exec_lock_contended() when num_objects is zero. This breaks the invariant upheld by drm_exec_lock_obj(), where every entry point into the locking sequence must first attempt to lock any previously contended object before proceeding. Drivers that chain multiple drm_exec_prepare_array() calls per drm_exec_until_all_locked() iteration (e.g. amdgpu's userq signal/wait ioctls, which prepare separate read and write BO arrays) can pass an empty array for one of the two calls. If contention is hit while preparing the non-empty array, exec->contended is set and the loop retries; on retry, the empty-array call preceding it is a no-op that never clears exec->contended, so drm_exec_retry_on_contention() immediately jumps back to the top of the loop without ever reaching the call that would resolve the contention. This spins forever. Fix it by having drm_exec_prepare_array() call drm_exec_lock_contended() directly when num_objects is zero, so a pending contended object dont loop infinitely.

References

NVD — CVE-2026-97900 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-97900
git.kernel.org/stable/c/159720704d... WEB
https://git.kernel.org/stable/c/159720704d9d652b64390c11fb971e15b0a78d23
git.kernel.org/stable/c/506cfed91e... WEB
https://git.kernel.org/stable/c/506cfed91e50cc8055799480a2fde5a18f63a21c
git.kernel.org/stable/c/831cd124ce... WEB
https://git.kernel.org/stable/c/831cd124ce99c3e61266bed30519d52f7c26abed
git.kernel.org/stable/c/a565022c02... WEB
https://git.kernel.org/stable/c/a565022c02f218ec9789c2baf4690792e7a48cbb
git.kernel.org/stable/c/f3e7486601... WEB
https://git.kernel.org/stable/c/f3e74866018dab793ebee1fdf0ef34f7271d1f8c

Frequently Asked Questions

What is CVE-2026-97900?
CVE-2026-97900 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-97900?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-97900?
CVE-2026-97900 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-97900?
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-fx27-pfff-j2g5",
  "modified" : "2026-10-03T12:31:19Z",
  "published" : "2026-09-25T12:31:27Z",
  "aliases" : [ "CVE-2026-97900" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/drm_exec: fix up contended obj when num_objects is 0\n\ndrm_exec_prepare_array() silently returns success without calling\ndrm_exec_lock_contended() when num_objects is zero. This breaks the\ninvariant upheld by drm_exec_lock_obj(), where every entry point into\nthe locking sequence must first attempt to lock any previously\ncontended object before proceeding.\n\nDrivers that chain multiple drm_exec_prepare_array() calls per\ndrm_exec_until_all_locked() iteration (e.g. amdgpu's userq signal/wait\nioctls, which prepare separate read and write BO arrays) can pass an\nempty array for one of the two calls. If contention is hit while\npreparing the non-empty array, exec->contended is set and the loop\nretries; on retry, the empty-array call preceding it is a no-op that\nnever clears exec->contended, so drm_exec_retry_on_contention()\nimmediately jumps back to the top of the loop without ever reaching\nthe call that would resolve the contention. This spins forever.\n\nFix it by having drm_exec_prepare_array() call drm_exec_lock_contended()\ndirectly when num_objects is zero, so a pending contended object dont\nloop infinitely.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-97900"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/159720704d9d652b64390c11fb971e15b0a78d23"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/506cfed91e50cc8055799480a2fde5a18f63a21c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/831cd124ce99c3e61266bed30519d52f7c26abed"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a565022c02f218ec9789c2baf4690792e7a48cbb"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f3e74866018dab793ebee1fdf0ef34f7271d1f8c"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-25T11:17:16Z"
  }
}