bnxt_en: Propagate TPA buffer allocation failures in bnxt_queue_mem_alloc()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
In the Linux kernel's bnxt_en driver, a TPA buffer allocation failure can leave a receive ring partially initialized because the failure is not propagated. If hardware selects an uninitialized slot, the driver can pass a zero DMA address to the device. The input does not describe an attacker path, authentication requirement, or user interaction.
Engineers running Linux kernels with the bnxt_en driver should check their versions; affected versions are not specified.