- Vulnerability/
- CVE-2023-53134
CVE-2023-53134: bnxt_en: Avoid order-5 memory allocation for TPA data
First published: Fri May 02 2025(Updated: )
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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | =5.10.156 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/16f3aae1aa2dd89bc8d073a67f190af580386ae9
- https://git.kernel.org/stable/c/d16701a385b54f44bf41ff1d7485e7a11080deb3
- https://git.kernel.org/stable/c/20fd0607acbf9770db9b99e3418dd75614f80b6c
- https://git.kernel.org/stable/c/fcae40e65802547def39b4deaa2ae38a29864d81
- https://git.kernel.org/stable/c/ad529d1fae1565d38f929479d4ea8aea90054bd2
- https://git.kernel.org/stable/c/accd7e23693aaaa9aa0d3e9eca0ae77d1be80ab3
Frequently Asked Questions
What is the severity of CVE-2023-53134?
The severity of CVE-2023-53134 has been classified as moderate.
What systems are affected by CVE-2023-53134?
CVE-2023-53134 affects the Linux kernel version 5.10.156.
How do I fix CVE-2023-53134?
To fix CVE-2023-53134, ensure that you update your Linux kernel to the latest version that addresses this vulnerability.
What type of vulnerability is CVE-2023-53134?
CVE-2023-53134 is related to memory allocation issues in the bnxt_en driver of the Linux kernel.
Is CVE-2023-53134 exploitable in the wild?
As of now, there is no public indication that CVE-2023-53134 is actively being exploited in the wild.
- collector/mitre-cve
- source/MITRE
- agent/title
- agent/references
- agent/type
- agent/description
- agent/first-publish-date
- agent/guess-ai
- agent/software-canonical-lookup
- agent/softwarecombine
- collector/nvd-api
- source/NVD
- agent/author
- agent/source
- agent/last-modified-date
- agent/tags
- agent/event
- vendor/linux
- canonical/linux kernel