{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97569 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-97569 is a denial of service vulnerability in Linux, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-97569 and fix it if it is affected.\n\nWhat it is: CVE-2026-97569 is a denial of service vulnerability in Linux, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-97569 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-97569/ (Markdown: https://insights.sbomify.com/CVE-2026-97569/index.md)","id":"CVE-2026-97569","markdown":"https://insights.sbomify.com/CVE-2026-97569/index.md","name":"CVE-2026-97569","record":{"aliases":["DEBIAN-CVE-2026-97569","GHSA-8qg4-f3vx-ghvf","UBUNTU-CVE-2026-97569"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A flaw in the bnxt_en driver allows remote attackers to cause a network queue hang and denial of service by sending specific packet bursts to systems with small ring buffers.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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 (\u003c= 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"bnxt_en: Prevent queue stop with deferred completions","id":"CVE-2026-97569","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"bnxt_en: Bound SW TPA IDs to prevent crashes","id":"CVE-2026-97570"},"packages":[],"prev":{"headline":"mptcp: syncookies: remember the request backup flag","id":"CVE-2026-97568"},"products":["Linux"],"published":"2026-09-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A flaw in the bnxt_en driver allows remote attackers to cause a network queue hang and denial of service by sending specific packet bursts to systems with small ring buffers.","url":"https://insights.sbomify.com/CVE-2026-97569/"}