CVE-2023-53134: bnxt_en: Avoid order-5 memory allocation for TPA data
Noroxi assessment
Priority: Monitor (action score 22/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.18% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 16f3aae1aa2dd89bc8d073a67f190af580386ae9, 20fd0607acbf9770db9b99e3418dd75614f80b6c, accd7e23693aaaa9aa0d3e9eca0ae77d1be80ab3.
Low priority for now. Upgrade to Linux Linux 16f3aae1aa2dd89bc8d073a67f190af580386ae9, 20fd0607acbf9770db9b99e3418dd75614f80b6c, accd7e23693aaaa9aa0d3e9eca0ae77d1be80ab3 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: Avoid order-5 memory allocation for TPA data The driver needs to keep track of all the possible concurrent TPA (GRO/LRO) completions on the aggregation ring. On P5 chips, the maximum number of concurrent TPA is 256 and the amount of memory we allocate is order-5 on systems using 4K pages. Memory allocation failure has been reported: NetworkManager: page allocation failure: order:5, mode:0x40dc0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null),cpuset=/,mems_allowed=0-1 CPU: 15 PID: 2995 Comm: NetworkManager Kdump: loaded Not tainted 5.10.156 #1 Hardware name: Dell Inc. PowerEdge R660/0M1CC5, BIOS 0.2.25 08/12/2022 Call Trace: dump_stack+0x57/0x6e warn_alloc.cold.120+0x7b/0xdd ? _cond_resched+0x15/0x30 ? __alloc_pages_direct_compact+0x15f/0x170 __alloc_pages_slowpath.constprop.108+0xc58/0xc70 __alloc_pages_nodemask+0x2d0/0x300 kmalloc_order+0x24/0xe0 kmalloc_order_trace+0x19/0x80 bnxt_alloc_mem+0x1150/0x15c0 [bnxt_en] ? bnxt_get_func_stat_ctxs+0x13/0x60 [bnxt_en] __bnxt_open_nic+0x12e/0x780 [bnxt_en] bnxt_open+0x10b/0x240 [bnxt_en] __dev_open+0xe9/0x180 __dev_change_flags+0x1af/0x220 dev_change_flags+0x21/0x60 do_setlink+0x35c/0x1100 Instead of allocating this big chunk of memory and dividing it up for the concurrent TPA instances, allocate each small chunk separately for each TPA instance. This will reduce it to order-0 allocations.
- Published
- May 2, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 8th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.4 and later · before 5.4.237
- linux linux kernel5.5 and later · before 5.10.175
- linux linux kernel5.11 and later · before 5.15.103
- linux linux kernel5.16 and later · before 6.1.20
- linux linux kernel6.2 and later · before 6.2.7
- linux linux kernel6.3
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.4affected
- 79632e9ba38671215fb193346ef6fb8db582744d and later · before 16f3aae1aa2dd89bc8d073a67f190af580386ae9affected · git
- 79632e9ba38671215fb193346ef6fb8db582744d and later · before d16701a385b54f44bf41ff1d7485e7a11080deb3affected · git
- 79632e9ba38671215fb193346ef6fb8db582744d and later · before 20fd0607acbf9770db9b99e3418dd75614f80b6caffected · git
- 79632e9ba38671215fb193346ef6fb8db582744d and later · before fcae40e65802547def39b4deaa2ae38a29864d81affected · git
- 79632e9ba38671215fb193346ef6fb8db582744d and later · before ad529d1fae1565d38f929479d4ea8aea90054bd2affected · git
- 79632e9ba38671215fb193346ef6fb8db582744d and later · before accd7e23693aaaa9aa0d3e9eca0ae77d1be80ab3affected · git
- before 5.4not affected · semver
- 5.4.237 and later · up to and including 5.4.*not affected · semver
- 5.10.175 and later · up to and including 5.10.*not 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.20-1 | 6.1.20-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2023-53132May 2, 2025 · scsi: mpi3mr: Fix mpi3mr_hba_port memory leak in mpi3mr_remove()22Monitor
- ← EarlierCVE-2023-53133May 2, 2025 · bpf, sockmap: Fix an infinite loop error when len is 0 in tcp_bpf_recvmsg_parser()22Monitor
- Later →CVE-2023-53135May 2, 2025 · riscv: Use READ_ONCE_NOCHECK in imprecise unwinding stack mode28Monitor
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 | 16f3aae1aa2dd89bc8d073a67f190af580386ae9 | Vendor (CNA) |
| Linux Linux | 20fd0607acbf9770db9b99e3418dd75614f80b6c | Vendor (CNA) |
| Linux Linux | accd7e23693aaaa9aa0d3e9eca0ae77d1be80ab3 | Vendor (CNA) |
| Linux Linux | ad529d1fae1565d38f929479d4ea8aea90054bd2 | Vendor (CNA) |
| Linux Linux | d16701a385b54f44bf41ff1d7485e7a11080deb3 | Vendor (CNA) |
| Linux Linux | fcae40e65802547def39b4deaa2ae38a29864d81 | Vendor (CNA) |
| debian:linux | 6.1.20-1 · 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.
No history yet (it accumulates with the daily EPSS job).
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).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
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 (5 more)Show less
- git.kernel.org/stable/c/20fd0607acbf9770db9b99e3418dd75614f80b6c
- git.kernel.org/stable/c/accd7e23693aaaa9aa0d3e9eca0ae77d1be80ab3
- git.kernel.org/stable/c/ad529d1fae1565d38f929479d4ea8aea90054bd2
- git.kernel.org/stable/c/d16701a385b54f44bf41ff1d7485e7a11080deb3
- git.kernel.org/stable/c/fcae40e65802547def39b4deaa2ae38a29864d81
Vendor advisories and official records. Exploit/PoC links are deliberately left out.