CVE-2023-53134

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> bnxt_en: Avoid order-5 memory allocation for TPA data<br /> <br /> The driver needs to keep track of all the possible concurrent TPA (GRO/LRO)<br /> completions on the aggregation ring. On P5 chips, the maximum number<br /> of concurrent TPA is 256 and the amount of memory we allocate is order-5<br /> on systems using 4K pages. Memory allocation failure has been reported:<br /> <br /> NetworkManager: page allocation failure: order:5, mode:0x40dc0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null),cpuset=/,mems_allowed=0-1<br /> CPU: 15 PID: 2995 Comm: NetworkManager Kdump: loaded Not tainted 5.10.156 #1<br /> Hardware name: Dell Inc. PowerEdge R660/0M1CC5, BIOS 0.2.25 08/12/2022<br /> Call Trace:<br /> dump_stack+0x57/0x6e<br /> warn_alloc.cold.120+0x7b/0xdd<br /> ? _cond_resched+0x15/0x30<br /> ? __alloc_pages_direct_compact+0x15f/0x170<br /> __alloc_pages_slowpath.constprop.108+0xc58/0xc70<br /> __alloc_pages_nodemask+0x2d0/0x300<br /> kmalloc_order+0x24/0xe0<br /> kmalloc_order_trace+0x19/0x80<br /> bnxt_alloc_mem+0x1150/0x15c0 [bnxt_en]<br /> ? bnxt_get_func_stat_ctxs+0x13/0x60 [bnxt_en]<br /> __bnxt_open_nic+0x12e/0x780 [bnxt_en]<br /> bnxt_open+0x10b/0x240 [bnxt_en]<br /> __dev_open+0xe9/0x180<br /> __dev_change_flags+0x1af/0x220<br /> dev_change_flags+0x21/0x60<br /> do_setlink+0x35c/0x1100<br /> <br /> Instead of allocating this big chunk of memory and dividing it up for the<br /> concurrent TPA instances, allocate each small chunk separately for each<br /> TPA instance. This will reduce it to order-0 allocations.