Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-97572

bnxt_en: Propagate RX ring init failures in bnxt_init_nic()

Description

In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Propagate RX ring init failures in bnxt_init_nic() bnxt_init_rx_rings() returns an error when bnxt_alloc_one_rx_ring() fails, but bnxt_init_nic() discards that return value and calls bnxt_init_chip(), which enables TPA. If an allocation fails, this could leave rxr->rx_tpa[] partially zeroed and TPA would be enabled over an array with zeroed entries. This would lead to a zeroed DMA address being handed out if the agg_idx is translated to a SW index at a zeroed entry. Fix this by propagating the error out of bnxt_init_nic(). Both callers already check its return value and unwind with bnxt_free_skbs() and bnxt_free_mem(), which tolerate a partially initialized RX ring.

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 24 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (12 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected c0c050c58d840994ba842ad1c338a98e7c12b764 – < e40641638743b4b848d5ed78a0565afffc359d8e
    • affected c0c050c58d840994ba842ad1c338a98e7c12b764 – < 6b24eca42619b93f69aebc2aa0a9fd28ac9a5085
    • affected c0c050c58d840994ba842ad1c338a98e7c12b764 – < 1f2d333ae2e1a73b7cc1c2a627587024cd147c01
    • affected c0c050c58d840994ba842ad1c338a98e7c12b764 – < c3eb07e78e628243cbb9bbb0115db802fb7a303f
    • affected c0c050c58d840994ba842ad1c338a98e7c12b764 – < daadccd062fdca5e77a8cc22ffe35857803b6c49
    • affected c0c050c58d840994ba842ad1c338a98e7c12b764 – < b4c40f2c80d7bf50648878bc206a39adfbfaec6c
    • affected c0c050c58d840994ba842ad1c338a98e7c12b764 – < dfd73af81cdb9f7b399754a59e2658a08211bee5
    • affected c0c050c58d840994ba842ad1c338a98e7c12b764 – < 8e6a850c0746bb4be167aedf1ee57469fcda09a9
  • Linux · Linux

    • affected 4.4
    • unaffected < 4.4
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2.7 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-97572 badge
[![CVE-2026-97572](https://cveledger.app/badge/CVE-2026-97572.svg)](https://cveledger.app/cve/CVE-2026-97572)

Record last updated .