bnxt_en: Handle buffer allocation failure in bnxt_rx_ring_reset()
Noroxi assessment
Priority: Monitor (action score 32/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.59% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Linux Linux 1a3670b6a6b5679fe56c5890157b344f091e64f8, 40b4a7bb6b0b872b45f017dbf211268de098b75c, 4a17c73c83798c2fa9c7920ad5a98803adce3e01; 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 1a3670b6a6b5679fe56c5890157b344f091e64f8, 40b4a7bb6b0b872b45f017dbf211268de098b75c, 4a17c73c83798c2fa9c7920ad5a98803adce3e01; 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: 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.
- Published
- Sep 25, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.5% · 47th percentile
- CWE
- —
Report tools
Action score
32
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.1
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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
- 5.10affected
- 8fbf58e17dce8f250dda9ad6b0a49b3041f0af14 and later · before 52fc97cbc3ba118aad84e7c001bf02ebe8496f70affected · git
- 8fbf58e17dce8f250dda9ad6b0a49b3041f0af14 and later · before 40b4a7bb6b0b872b45f017dbf211268de098b75caffected · git
- 8fbf58e17dce8f250dda9ad6b0a49b3041f0af14 and later · before af9a2bdaba0b4ceb0fc5e5122ef3fc6b7e5a366aaffected · git
- 8fbf58e17dce8f250dda9ad6b0a49b3041f0af14 and later · before cfec9e7f15a56cb0104bac13d01e5d11e1ba84fbaffected · git
- 8fbf58e17dce8f250dda9ad6b0a49b3041f0af14 and later · before 1a3670b6a6b5679fe56c5890157b344f091e64f8affected · git
- 8fbf58e17dce8f250dda9ad6b0a49b3041f0af14 and later · before 4a17c73c83798c2fa9c7920ad5a98803adce3e01affected · git
- 8fbf58e17dce8f250dda9ad6b0a49b3041f0af14 and later · before 8b2fd5c0aeda935294159206af9d6179282d425aaffected · git
- 8fbf58e17dce8f250dda9ad6b0a49b3041f0af14 and later · before 961e2a17c5e3559b3f8654d2daabdd25a42e770aaffected · git
- before 5.10not 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-97571Sep 25, 2026 · bnxt_en: Propagate TPA buffer allocation failures in bnxt_queue_mem_alloc()0Monitor
- ← EarlierCVE-2026-97572Sep 25, 2026 · bnxt_en: Propagate RX ring init failures in bnxt_init_nic()0Monitor
- Later →CVE-2026-97574Sep 25, 2026 · bnxt_en: Don't free the live ring's TPA state on queue restart failure0Monitor
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 | 1a3670b6a6b5679fe56c5890157b344f091e64f8 | Vendor (CNA) |
| Linux Linux | 40b4a7bb6b0b872b45f017dbf211268de098b75c | Vendor (CNA) |
| Linux Linux | 4a17c73c83798c2fa9c7920ad5a98803adce3e01 | Vendor (CNA) |
| Linux Linux | 52fc97cbc3ba118aad84e7c001bf02ebe8496f70 | Vendor (CNA) |
| Linux Linux | 8b2fd5c0aeda935294159206af9d6179282d425a | Vendor (CNA) |
| Linux Linux | 961e2a17c5e3559b3f8654d2daabdd25a42e770a | Vendor (CNA) |
| Linux Linux | af9a2bdaba0b4ceb0fc5e5122ef3fc6b7e5a366a | Vendor (CNA) |
| Linux Linux | cfec9e7f15a56cb0104bac13d01e5d11e1ba84fb | 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
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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/40b4a7bb6b0b872b45f017dbf211268de098b75c
- git.kernel.org/stable/c/4a17c73c83798c2fa9c7920ad5a98803adce3e01
- git.kernel.org/stable/c/52fc97cbc3ba118aad84e7c001bf02ebe8496f70
- git.kernel.org/stable/c/8b2fd5c0aeda935294159206af9d6179282d425a
- git.kernel.org/stable/c/961e2a17c5e3559b3f8654d2daabdd25a42e770a
- git.kernel.org/stable/c/af9a2bdaba0b4ceb0fc5e5122ef3fc6b7e5a366a
- git.kernel.org/stable/c/cfec9e7f15a56cb0104bac13d01e5d11e1ba84fb
Vendor advisories and official records. Exploit/PoC links are deliberately left out.