bnxt_en: Propagate RX ring init failures in bnxt_init_nic()
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 1f2d333ae2e1a73b7cc1c2a627587024cd147c01, 6b24eca42619b93f69aebc2aa0a9fd28ac9a5085, 8e6a850c0746bb4be167aedf1ee57469fcda09a9; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 1f2d333ae2e1a73b7cc1c2a627587024cd147c01, 6b24eca42619b93f69aebc2aa0a9fd28ac9a5085, 8e6a850c0746bb4be167aedf1ee57469fcda09a9; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 25, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.4affected
- c0c050c58d840994ba842ad1c338a98e7c12b764 and later · before e40641638743b4b848d5ed78a0565afffc359d8eaffected · git
- c0c050c58d840994ba842ad1c338a98e7c12b764 and later · before 6b24eca42619b93f69aebc2aa0a9fd28ac9a5085affected · git
- c0c050c58d840994ba842ad1c338a98e7c12b764 and later · before 1f2d333ae2e1a73b7cc1c2a627587024cd147c01affected · git
- c0c050c58d840994ba842ad1c338a98e7c12b764 and later · before c3eb07e78e628243cbb9bbb0115db802fb7a303faffected · git
- c0c050c58d840994ba842ad1c338a98e7c12b764 and later · before daadccd062fdca5e77a8cc22ffe35857803b6c49affected · git
- c0c050c58d840994ba842ad1c338a98e7c12b764 and later · before b4c40f2c80d7bf50648878bc206a39adfbfaec6caffected · git
- c0c050c58d840994ba842ad1c338a98e7c12b764 and later · before dfd73af81cdb9f7b399754a59e2658a08211bee5affected · git
- c0c050c58d840994ba842ad1c338a98e7c12b764 and later · before 8e6a850c0746bb4be167aedf1ee57469fcda09a9affected · git
- before 4.4not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.7-1 | 7.2.7-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-97570Sep 25, 2026 · bnxt_en: Bound SW TPA IDs to prevent crashes32Monitor
- ← EarlierCVE-2026-97571Sep 25, 2026 · bnxt_en: Propagate TPA buffer allocation failures in bnxt_queue_mem_alloc()0Monitor
- Later →CVE-2026-97573Sep 25, 2026 · bnxt_en: Handle buffer allocation failure in bnxt_rx_ring_reset()32Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1f2d333ae2e1a73b7cc1c2a627587024cd147c01 | Vendor (CNA) |
| Linux Linux | 6b24eca42619b93f69aebc2aa0a9fd28ac9a5085 | Vendor (CNA) |
| Linux Linux | 8e6a850c0746bb4be167aedf1ee57469fcda09a9 | Vendor (CNA) |
| Linux Linux | b4c40f2c80d7bf50648878bc206a39adfbfaec6c | Vendor (CNA) |
| Linux Linux | c3eb07e78e628243cbb9bbb0115db802fb7a303f | Vendor (CNA) |
| Linux Linux | daadccd062fdca5e77a8cc22ffe35857803b6c49 | Vendor (CNA) |
| Linux Linux | dfd73af81cdb9f7b399754a59e2658a08211bee5 | Vendor (CNA) |
| Linux Linux | e40641638743b4b848d5ed78a0565afffc359d8e | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.158.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1184 · Sep 28, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/6b24eca42619b93f69aebc2aa0a9fd28ac9a5085
- git.kernel.org/stable/c/8e6a850c0746bb4be167aedf1ee57469fcda09a9
- git.kernel.org/stable/c/b4c40f2c80d7bf50648878bc206a39adfbfaec6c
- git.kernel.org/stable/c/c3eb07e78e628243cbb9bbb0115db802fb7a303f
- git.kernel.org/stable/c/daadccd062fdca5e77a8cc22ffe35857803b6c49
- git.kernel.org/stable/c/dfd73af81cdb9f7b399754a59e2658a08211bee5
- git.kernel.org/stable/c/e40641638743b4b848d5ed78a0565afffc359d8e
Vendor advisories and official records. Exploit/PoC links are deliberately left out.