Vulnerability · Published Sep 25, 2026 · Assigned by Linux

CVE-2026-97569bnxt_en: Prevent queue stop with deferred completions

Unrated

In plain English

A security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 11% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 88.7% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:14linux7.2.7-1DEBIAN-CVE-2026-97569
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-97569
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-97569
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-97569
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-97569
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-97569
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-97569
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-97569
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-97569
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-97569
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-97569
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-97569
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-97569
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-97569
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-97569
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-97569
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-97569
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-97569
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-97569
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-97569
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-97569
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-97569
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-97569
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-97569
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-97569
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-97569
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-97569
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-97569
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-97569
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-97569
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-97569
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-97569
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-97569
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-97569
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-97569
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-97569
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-97569
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-97569
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-97569
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-97569
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-97569
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-97569
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-97569
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-97569
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-97569
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-97569
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-97569
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-97569
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-97569
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-97569
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-97569
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-97569
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-97569
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-97569
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-97569
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-97569
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-97569
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-97569
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-97569
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-97569

Affected products (as reported)

VendorProductVersions
Linux Linux cc5d90667db81474ed7a92a1b2fa3daec5559307 – before e33ce547c0cd40738d6bad23e5fc0539ee3e8f7dcc5d90667db81474ed7a92a1b2fa3daec5559307 – before 39b23c1c40e1f73d2b94a09282cc476af647e438
Linux Linux 7.1

References