bnxt_en: Propagate RX ring init failures in bnxt_init_nic()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ c0c050c58d840994ba842ad1c338a98e7c12b764 · < b4c40f2c80d7bf50648878bc206a39adfbfaec6c| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
bnxt_en: Propagate RX ring init failures in bnxt_init_nic()
bnxt_init_rx_rings() returns an error when bnxt_alloc_one_rx_ring() fails, but bnxt_init_nic() discards that return value and calls bnxt_init_chip(), which enables TPA.
If an allocation fails, this could leave rxr->rx_tpa[] partially zeroed and TPA would be enabled over an array with zeroed entries. This would lead to a zeroed DMA address being handed out if the agg_idx is translated to a SW index at a zeroed entry.
Fix this by propagating the error out of bnxt_init_nic(). Both callers already check its return value and unwind with bnxt_free_skbs() and bnxt_free_mem(), which tolerate a partially initialized RX ring.
From the CVE record · Linux
The bnxt_en driver can enable TPA after an RX ring allocation fails, potentially causing it to hand out a zeroed DMA address. The input does not describe an attacker action or specify network access, authentication, or user interaction requirements.
Engineers running Linux kernels with the bnxt_en driver should check their installations; affected versions are not specified.