bnxt_en: Propagate TPA buffer allocation failures in bnxt_queue_mem_alloc()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel c8050386a2209b2a474c1eb4bd1574dc19129bfb, Kernel 6.12.112, Kernel 37e08dc821a57fe0592c917486b638caa888b46d and 4 more.
In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Propagate TPA buffer allocation failures in bnxt_queue_mem_alloc() bnxt_alloc_one_tpa_info_data() returns -ENOMEM as soon as one allocation fails. This leaves the remaining rxr->rx_tpa[] entries zeroed. bnxt_queue_mem_alloc() discards that return value, so the partially initialized ring is installed by bnxt_queue_start(). Since the agg_id is picked by the hardware and bnxt_alloc_agg_idx maps it to a SW index in rxr->rx_tpa[], it is possible that an uninitialized slot can be chosen which would hand a zero DMA address to the device. Fix this by checking the return value of bnxt_alloc_one_tpa_info_data and unwinding, freeing the ring buffers.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=bd649c5cc958169b8a8a3e77ea926d92d472b02a <c8050386a2209b2a474c1eb4bd1574dc19129bfb, >=6.12.20 <6.12.112, >=bd649c5cc958169b8a8a3e77ea926d92d472b02a <37e08dc821a57fe0592c917486b638caa888b46d, >=bd649c5cc958169b8a8a3e77ea926d92d472b02a <b814dfbfeb0a68c9a52073f2caa05a2d5247a329, =6.13, >=0997443906b96a051011f220a61e6dce4602ec54 <d7db2e4953e4626339fd0075564a3e447650d37b | c8050386a2209b2a474c1eb4bd1574dc19129bfb, 6.12.112, 37e08dc821a57fe0592c917486b638caa888b46d, b814dfbfeb0a68c9a52073f2caa05a2d5247a329, d7db2e4953e4626339fd0075564a3e447650d37b |
| linux-kernel: Kernel | >=6.13.0 <6.18.53, >=6.19.0 <7.2.7, >=6.12.20 <6.12.112 | 6.18.53, 7.2.7, 6.12.112 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket