CVE-2026-97979: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-f354-573p-458p
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-97979
GHSA Identifier GHSA-f354-573p-458p
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-97979

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-97979, 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: ice: add missing xa_destroy for sched_node_ids Commit 16dfa49406bc ("ice: Introduce new parameters in ice_sched_node") added a sched_node_ids xarray to the port info structure, but never called xa_destroy on it. Since xarrays can allocate internal memory, this can result in a memory leak even if every element in the xarray has been removed. The xarray is currently embedded in the port_info structure. This appears to have been done because its use is within functions that take the port_info as a primary argument. However, this complicates managing the lifecycle of the field. The port_info structure is allocated in ice_init_hw() using devm, and it is not released until the devm cleanup when the driver is unloaded. The ice_init_hw() function is called in many places, including devlink reload, and possibly during DDP load after updating the Tx scheduler layout. Adding a call of xa_destroy to the ice_deinit_hw() causes Sashiko to raise multiple concerns due to potential ordering issues and possible ways that port_info could be a dangling reference. To handle this, move the sched_node_ids out of port_info and into the hw structure. All users of the array already have a pointer to hw anyways, and there is only one sched_node_ids per adapter. While here, remove the overly verbose comment explaining the nature of the sched_node_ids xarray. Add the missing xa_destroy to the cleanup path and to ice_deinit_hw(), ensuring that we properly release the xarray memory. This was caught by Sashiko during development of unrelated code.

References

NVD — CVE-2026-97979 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-97979
git.kernel.org/stable/c/09a7cdf8ff... WEB
https://git.kernel.org/stable/c/09a7cdf8fffb065a8aa30cfa604ff4a65cbf04c9
git.kernel.org/stable/c/44cdd6b7e0... WEB
https://git.kernel.org/stable/c/44cdd6b7e036303f7fecf841cf23c05a4a4faf2d
git.kernel.org/stable/c/53432c4c3e... WEB
https://git.kernel.org/stable/c/53432c4c3e869076350aef319534431af8ba99c1
git.kernel.org/stable/c/c075a91fe5... WEB
https://git.kernel.org/stable/c/c075a91fe5762d314e6e182d37d29cf874bd314a
git.kernel.org/stable/c/d6f38fb120... WEB
https://git.kernel.org/stable/c/d6f38fb12069fb1edf762962b5fcf3f42d643b47
git.kernel.org/stable/c/f5463bc124... WEB
https://git.kernel.org/stable/c/f5463bc124c0d6f922e272336584730c5c61c4f1

Frequently Asked Questions

What is CVE-2026-97979?
CVE-2026-97979 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-97979?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-97979?
CVE-2026-97979 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-97979?
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-f354-573p-458p",
  "modified" : "2026-10-03T12:31:23Z",
  "published" : "2026-09-25T12:31:31Z",
  "aliases" : [ "CVE-2026-97979" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nice: add missing xa_destroy for sched_node_ids\n\nCommit 16dfa49406bc (\"ice: Introduce new parameters in ice_sched_node\")\nadded a sched_node_ids xarray to the port info structure, but never called\nxa_destroy on it.\n\nSince xarrays can allocate internal memory, this can result in a memory\nleak even if every element in the xarray has been removed.\n\nThe xarray is currently embedded in the port_info structure. This appears\nto have been done because its use is within functions that take the\nport_info as a primary argument.\n\nHowever, this complicates managing the lifecycle of the field. The\nport_info structure is allocated in ice_init_hw() using devm, and it is\nnot released until the devm cleanup when the driver is unloaded.\n\nThe ice_init_hw() function is called in many places, including devlink\nreload, and possibly during DDP load after updating the Tx scheduler\nlayout.\n\nAdding a call of xa_destroy to the ice_deinit_hw() causes Sashiko to raise\nmultiple concerns due to potential ordering issues and possible ways that\nport_info could be a dangling reference.\n\nTo handle this, move the sched_node_ids out of port_info and into the hw\nstructure. All users of the array already have a pointer to hw anyways, and\nthere is only one sched_node_ids per adapter. While here, remove the overly\nverbose comment explaining the nature of the sched_node_ids xarray.\n\nAdd the missing xa_destroy to the cleanup path and to ice_deinit_hw(),\nensuring that we properly release the xarray memory.\n\nThis was caught by Sashiko during development of unrelated code.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-97979"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/09a7cdf8fffb065a8aa30cfa604ff4a65cbf04c9"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/44cdd6b7e036303f7fecf841cf23c05a4a4faf2d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/53432c4c3e869076350aef319534431af8ba99c1"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c075a91fe5762d314e6e182d37d29cf874bd314a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d6f38fb12069fb1edf762962b5fcf3f42d643b47"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f5463bc124c0d6f922e272336584730c5c61c4f1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-25T11:17:25Z"
  }
}