CVE-2026-97569: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-8qg4-f3vx-ghvf
Published
Advisory Summary

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

CVE Identifier CVE-2026-97569
GHSA Identifier GHSA-8qg4-f3vx-ghvf
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-97569

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-97569, 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: bnxt_en: Prevent queue stop with deferred completions When the driver receives a burst of packets, it can mark a BD with the NO_CMPL bit to defer completions. The expectation is that the last packet in the ring will have this bit unset and the completion generated by that packet will cleanup that packet and the ones preceding it. This helps to reduce the number of completions fired. The suppressed completions are controlled by the driver and the number of packets with suppressed completions scales with the size of the ring. SW USO packets, on the other hand, have an upper bound on the maximum number of BDs which can be consumed which does not scale with the ring size. So, for small rings it is possible that: a burst of packets is handed to the driver, the driver defers completions for all of the packets because the number of free descriptors stays above the threshold in the driver. Then, a USO packet arrives, but the number of BDs available is not enough and the USO code exits early. In this case, you end up in a state where the ring is full of packets with their completions suppressed, which can cause the queue to stop and never be restarted. Assuming default CONFIG_MAX_SKB_FRAGS, this is only possible for small rings (<= 457 descriptors, below the driver default value) when a burst of packets fills the ring, followed by a large USO packet that can't fit. For larger rings, the delta between the completion suppression threshold and the BDs required for SW USO is large enough that completions will fire and this case is unreachable. This issue was pointed out by Sashiko and while it seems fairly unlikely given that the queue size must be small to trigger this, it is indeed possible. Fix this by tracking the last BD which deferred completions and centralizing the logic for deciding when to ring the doorbell. The NO_CMPL bit is now cleared in bnxt_txr_db_kick(), so every doorbell site is covered, including the SW USO early exit. This guarantees the ring always ends in a BD which generates a completion to clean it and wake the queue.

References

Frequently Asked Questions

What is CVE-2026-97569?
CVE-2026-97569 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-97569?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-97569?
CVE-2026-97569 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-97569?
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-8qg4-f3vx-ghvf",
  "modified" : "2026-09-25T12:31:24Z",
  "published" : "2026-09-25T12:31:24Z",
  "aliases" : [ "CVE-2026-97569" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nbnxt_en: Prevent queue stop with deferred completions\n\nWhen the driver receives a burst of packets, it can mark a BD with the\nNO_CMPL bit to defer completions. The expectation is that the last\npacket in the ring will have this bit unset and the completion generated\nby that packet will cleanup that packet and the ones preceding it. This\nhelps to reduce the number of completions fired.\n\nThe suppressed completions are controlled by the driver and the number\nof packets with suppressed completions scales with the size of the ring.\nSW USO packets, on the other hand, have an upper bound on the maximum\nnumber of BDs which can be consumed which does not scale with the ring\nsize.\n\nSo, for small rings it is possible that: a burst of packets is handed to\nthe driver, the driver defers completions for all of the packets because\nthe number of free descriptors stays above the threshold in the driver.\nThen, a USO packet arrives, but the number of BDs available is not\nenough and the USO code exits early.\n\nIn this case, you end up in a state where the ring is full of packets\nwith their completions suppressed, which can cause the queue to stop and\nnever be restarted.\n\nAssuming default CONFIG_MAX_SKB_FRAGS, this is only possible for small\nrings (<= 457 descriptors, below the driver default value) when\na burst of packets fills the ring, followed by a large USO packet that\ncan't fit. For larger rings, the delta between the completion\nsuppression threshold and the BDs required for SW USO is large enough\nthat completions will fire and this case is unreachable.\n\nThis issue was pointed out by Sashiko and while it seems fairly unlikely\ngiven that the queue size must be small to trigger this, it is indeed\npossible.\n\nFix this by tracking the last BD which deferred completions and\ncentralizing the logic for deciding when to ring the doorbell. The NO_CMPL\nbit is now cleared in bnxt_txr_db_kick(), so every doorbell site is\ncovered, including the SW USO early exit. This guarantees the ring always\nends in a BD which generates a completion to clean it and wake the queue.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-97569"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/39b23c1c40e1f73d2b94a09282cc476af647e438"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e33ce547c0cd40738d6bad23e5fc0539ee3e8f7d"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-25T11:17:07Z"
  }
}