CVE-2026-97514: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-8mx9-7h8g-9qqg
Published
Advisory Summary

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

CVE Identifier CVE-2026-97514
GHSA Identifier GHSA-8mx9-7h8g-9qqg
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-97514

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-97514, 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: media: chips-media: wave5: Fix Reports from Kernel Lock Validator handle_dynamic_resolution change requires that the state_lock be acquired based on the lockdep_assert_held. However, the handle_dynamic_resolution_change call in initialize_sequence does not properly obtain the lock before calling. Since the v4l2_ctrl_find and s_ctrl can sleep, they should not be called while a lock is already held. Store off the fbc_buf_count then properly update control once lock has been freed.

References

Frequently Asked Questions

What is CVE-2026-97514?
CVE-2026-97514 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-97514?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-97514?
CVE-2026-97514 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-97514?
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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-8mx9-7h8g-9qqg",
  "modified" : "2026-09-24T18:31:35Z",
  "published" : "2026-09-24T18:31:35Z",
  "aliases" : [ "CVE-2026-97514" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: chips-media: wave5: Fix Reports from Kernel Lock Validator\n\nhandle_dynamic_resolution change requires that the state_lock be acquired\nbased on the lockdep_assert_held. However, the\nhandle_dynamic_resolution_change call in initialize_sequence does not\nproperly obtain the lock before calling.\n\nSince the v4l2_ctrl_find and s_ctrl can sleep, they should not be called\nwhile a lock is already held. Store off the fbc_buf_count then properly\nupdate control once lock has been freed.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-97514"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/072beef6a19f9c84dc5a50c5499663a5734c1096"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/629a937091ecf9c5c9f7a18f41cb0e6c778a7b2f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7d5d364f8b2dcc9b6b92456fb55632fde4a4d96f"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-24T17:17:29Z"
  }
}