CVE-2026-97925: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-frpq-r7pw-xq84
Published
Advisory Summary

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

CVE Identifier CVE-2026-97925
GHSA Identifier GHSA-frpq-r7pw-xq84
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-97925

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-97925, 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: tick/broadcast: Plug clockevents replacement race 朱恺乾 reported and decoded the following race condition when a broadcast device is replaced: CPUA CPUB __tick_broadcast_oneshot_control() bc = tick_broadcast_device.evtdev; tick_install_broadcast_device(dev) clockevents_exchange_device(cur, dev) shutdown(cur); detach(cur); cur->handler = noop; tick_broadcast_device.evtdev = dev; tick_broadcast_set_event(bc, next_event); <- FAIL: arms a detached device. If the original broadcast device has a restricted interrupt affinity mask and the last CPU in that mask goes offline then the BUG() in tick_cleanup_dead_cpu() triggers because the clockevent device is not in detached state. The reason for this is that tick_install_broadcast_device() is not serialized vs. tick broadcast operations. The obvious cure is to serialize tick_install_broadcast_device() with tick_broadcast_lock against a concurrent tick broadcast operation. That requires to split clockevents_exchange_device() into two parts, one which does the exchange, shutdown and detach operation and the other which drops the module reference count. This is required because the module reference cannot be dropped while holding tick_broadcast_lock. Let clockevents_exchange_device() do both operations as before, but let the broadcast device code take the two step approach and do the device exchange under tick_broadcast_lock and drop the module reference count after releasing it.

References

Frequently Asked Questions

What is CVE-2026-97925?
CVE-2026-97925 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-97925?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-97925?
CVE-2026-97925 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-97925?
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-frpq-r7pw-xq84",
  "modified" : "2026-10-03T12:31:20Z",
  "published" : "2026-09-25T12:31:28Z",
  "aliases" : [ "CVE-2026-97925" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ntick/broadcast: Plug clockevents replacement race\n\n朱恺乾 reported and decoded the following race condition when a broadcast\ndevice is replaced:\n\nCPUA\t\t\t\t\tCPUB\n __tick_broadcast_oneshot_control()\n   bc = tick_broadcast_device.evtdev;\n\t\t\t\t\ttick_install_broadcast_device(dev)\n        \t\t\t\tclockevents_exchange_device(cur, dev)\n\t\t\t\t\t   shutdown(cur);\n\t\t\t\t\t   detach(cur);\n\t\t\t\t\t   cur->handler = noop;\n\t\t\t\t\t   tick_broadcast_device.evtdev = dev;\n\n  tick_broadcast_set_event(bc, next_event); <- FAIL: arms a detached device.\n\nIf the original broadcast device has a restricted interrupt affinity mask\nand the last CPU in that mask goes offline then the BUG() in\ntick_cleanup_dead_cpu() triggers because the clockevent device is not in\ndetached state.\n\nThe reason for this is that tick_install_broadcast_device() is not\nserialized vs. tick broadcast operations.\n\nThe obvious cure is to serialize tick_install_broadcast_device() with\ntick_broadcast_lock against a concurrent tick broadcast operation.\n\nThat requires to split clockevents_exchange_device() into two parts, one\nwhich does the exchange, shutdown and detach operation and the other which\ndrops the module reference count. This is required because the module\nreference cannot be dropped while holding tick_broadcast_lock.\n\nLet clockevents_exchange_device() do both operations as before, but let the\nbroadcast device code take the two step approach and do the device\nexchange under tick_broadcast_lock and drop the module reference count\nafter releasing it.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-97925"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/113a9796effe3376d2ec5aabcca1fef4fef4cd62"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/292b7a8ed84032cfdfc9076a690360f7d3f640d4"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/338d6859cd1580617807290f6d7e92b1662d4695"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/3525b94b2f258e0b99d1ee5a82a80b51bc1cc818"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/3da55616db2b6b7d9caa3b7ff1e8983224e0ed52"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/757aa9f548c18b96da1d56d11f65be8188a16d59"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-25T11:17:19Z"
  }
}