CVE-2026-97573

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-09-25. A secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.1EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.1Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

In the Linux kernel, the following vulnerability has been resolved:

bnxt_en: Handle buffer allocation failure in bnxt_rx_ring_reset()

bnxt_rx_ring_reset() frees the ring buffers and then reallocates them, ignoring the result.

bnxt_alloc_one_rx_ring() can fail in bnxt_alloc_one_tpa_info_data(), which returns -ENOMEM on the first failed allocation and leaves the remaining rxr->rx_tpa[] entries zeroed.

The error isn't propagated up, so the loop in bnxt_rx_ring_reset continues and at the end the code re-enables TPA with partially unallocated rx_tpa array.

This means that when the agg_id from hardware is mapped to a SW index in rxr->rx_tpa[], an uninitialized slot can be chosen which would hand a zero DMA address to the device.

Fix this by falling back to a global reset, which is what the existing code already does when other functions fail, but unlike the other failure cases this particular failure has to return because TPA can't be re-enabled since the allocation failed.

CVSS v3
8.1
EG Score
8.1HIGHhigh confidence
EG Risk
41
EG Risk 41/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation1% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.6%
EPSS %ILE
46th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 25, 2026

Last Modified

October 3, 2026

Advisory Details (4)

Auto-updated Sep 25, 2026
No patch confirmed yet.
generic

bnxt_en: Handle buffer allocation failure in bnxt_rx_ring_reset() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/961e2a17c5e3559b3f8654d2daabdd25a42e770a
generic

bnxt_en: Handle buffer allocation failure in bnxt_rx_ring_reset() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8b2fd5c0aeda935294159206af9d6179282d425a
generic

bnxt_en: Handle buffer allocation failure in bnxt_rx_ring_reset() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4a17c73c83798c2fa9c7920ad5a98803adce3e01
generic

bnxt_en: Handle buffer allocation failure in bnxt_rx_ring_reset() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1a3670b6a6b5679fe56c5890157b344f091e64f8

Vendor Advisories for CVE-2026-97573(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (180 versions)
  • every version up to 7.2.7-1: fixed in 7.2.7-1
—

Data Freshness Timeline

(refreshed 40× in last 7d / 59× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-05 02:39 UTCEG score recompute
  2. 2026-10-05 02:39 UTCVendor advisory
  3. 2026-10-05 02:39 UTCGHSA enrichment
  4. 2026-10-04 23:23 UTCEPSS rescore
  5. 2026-10-04 13:36 UTCVendor advisory
  6. 2026-10-04 13:36 UTCGHSA enrichment
  7. 2026-10-04 00:32 UTCEG score recompute
  8. 2026-10-04 00:32 UTCVendor advisory
  9. 2026-10-04 00:32 UTCGHSA enrichment
  10. 2026-10-03 14:26 UTCEPSS rescore
  11. 2026-10-03 11:29 UTCVendor advisory
  12. 2026-10-03 11:29 UTCGHSA enrichment
  13. 2026-10-03 06:25 UTCEG score recompute
  14. 2026-10-03 06:25 UTCVendor advisory
  15. 2026-10-03 06:25 UTCGHSA enrichment
  16. 2026-10-02 17:57 UTCEPSS rescore
  17. 2026-10-02 17:21 UTCVendor advisory
  18. 2026-10-02 17:21 UTCGHSA enrichment
  19. 2026-10-02 04:16 UTCEG score recompute
  20. 2026-10-02 04:16 UTCVendor advisory
  21. 2026-10-02 04:16 UTCGHSA enrichment
  22. 2026-10-01 19:51 UTCEPSS rescore
  23. 2026-10-01 15:09 UTCVendor advisory
  24. 2026-10-01 15:09 UTCGHSA enrichment
  25. 2026-10-01 02:06 UTCEG score recompute
Show 34 more
  1. 2026-10-01 02:06 UTCVendor advisory
  2. 2026-10-01 02:06 UTCGHSA enrichment
  3. 2026-09-30 15:04 UTCEPSS rescore
  4. 2026-09-30 13:03 UTCVendor advisory
  5. 2026-09-30 13:02 UTCGHSA enrichment
  6. 2026-09-29 23:54 UTCEG score recompute
  7. 2026-09-29 23:54 UTCVendor advisory
  8. 2026-09-29 23:54 UTCGHSA enrichment
  9. 2026-09-29 10:50 UTCVendor advisory
  10. 2026-09-29 10:50 UTCGHSA enrichment
  11. 2026-09-28 21:47 UTCEG score recompute
  12. 2026-09-28 21:47 UTCVendor advisory
  13. 2026-09-28 21:47 UTCGHSA enrichment
  14. 2026-09-28 13:52 UTCEPSS rescore
  15. 2026-09-28 13:52 UTCEPSS rescore
  16. 2026-09-28 08:44 UTCVendor advisory
  17. 2026-09-28 08:44 UTCGHSA enrichment
  18. 2026-09-27 19:41 UTCEG score recompute
  19. 2026-09-27 19:41 UTCGHSA enrichment
  20. 2026-09-27 13:49 UTCEPSS rescore
  21. 2026-09-27 06:38 UTCGHSA enrichment
  22. 2026-09-26 17:35 UTCEG score recompute
  23. 2026-09-26 17:34 UTCGHSA enrichment
  24. 2026-09-26 15:59 UTCEPSS rescore
  25. 2026-09-26 04:30 UTCEG score recompute
  26. 2026-09-26 04:30 UTCGHSA enrichment
  27. 2026-09-25 15:26 UTCEG score recompute
  28. 2026-09-25 15:26 UTCGHSA enrichment
  29. 2026-09-25 14:52 UTCEG score recompute▲ 8.10
  30. 2026-09-25 14:52 UTCGHSA enrichment
  31. 2026-09-25 14:49 UTCMITRE cvelistV5CVSS v3 → 8.1 · severity → HIGH
  32. 2026-09-25 11:29 UTCNVD update
  33. 2026-09-25 10:40 UTCEG score recompute
  34. 2026-09-25 10:27 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-97573?
CVE-2026-97573 is a high vulnerability published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: bnxten: Handle buffer allocation failure in bnxtrxringreset() bnxtrxring_reset() frees the ring buffers and then reallocates them, ignoring the result. bnxtalloconerxring() can fail in bnxtalloconetpainfo_data(), which returns…
When was CVE-2026-97573 disclosed?
CVE-2026-97573 was first published on September 25, 2026, with the most recent update on October 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-97573 actively exploited?
CVE-2026-97573 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (46th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-97573?
CVE-2026-97573 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-97573?
No fix for CVE-2026-97573 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-97573 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-97573

Explore →

Is Your Infrastructure Affected by CVE-2026-97573?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs