CVE-2023-53134 Details
Description
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.
A denial-of-service vulnerability has been identified in the Linux kernel's bnxt_en driver, specifically in versions prior to 5.10.156. The issue arises from the driver allocating a large chunk of memory (order-5) on systems with 4K pages to manage concurrent TPA (TCP Segmentation Offload) completions. This excessive allocation can lead to memory allocation failures, as reported by NetworkManager. The vulnerability is particularly relevant for users with P5 chips, where the driver must handle up to 256 concurrent TPA instances.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/16f3aae1aa2dd89bc8d073a67f190af580386ae9 | kernel.org | Patch |
| https://git.kernel.org/stable/c/20fd0607acbf9770db9b99e3418dd75614f80b6c | kernel.org | Patch |
| https://git.kernel.org/stable/c/accd7e23693aaaa9aa0d3e9eca0ae77d1be80ab3 | kernel.org | Patch |
| https://git.kernel.org/stable/c/ad529d1fae1565d38f929479d4ea8aea90054bd2 | kernel.org | Patch |
| https://git.kernel.org/stable/c/d16701a385b54f44bf41ff1d7485e7a11080deb3 | kernel.org | Patch |
| https://git.kernel.org/stable/c/fcae40e65802547def39b4deaa2ae38a29864d81 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.4, < 5.4.237 >= 5.5, < 5.10.175 >= 5.11, < 5.15.103 >= 5.16, < 6.1.20 >= 6.2, < 6.2.7 6.3 rc1 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Nov 10, 2025 | Initial Analysis | [email protected] |
| May 2, 2025 | New CVE Received | kernel.org |