Linux
bnxt_en: Handle buffer allocation failure in bnxt_rx_ring_reset()
In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Handle buffer allocation failure in bnxt_rx_ring_reset() bnxt_rx_ring_reset() frees the ring buffers and then reallocates them, ignoring the result. bnxt_alloc_one_rx_ring() can fail in bnxt_alloc_one_tpa_info_data(), which returns -ENOMEM on the first failed allocation and leaves the remaining rxr->rx_tpa[] entries zeroed. The error isn't propagated up, so the loop in bnxt_rx_ring_reset continues and at the end the code re-enables TPA with partially unallocated rx_tpa array. This means that when the agg_id from hardware is mapped to a SW index in rxr->rx_tpa[], an uninitialized slot can be chosen which would hand a zero DMA address to the device. Fix this by falling back to a global reset, which is what the existing code already does when other functions fail, but unlike the other failure cases this particular failure has to return because TPA can't be re-enabled since the allocation failed.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 8fbf58e17dce8f250dda9ad6b0a49b3041f0af14, < 52fc97cbc3ba118aad84e7c001bf02ebe8496f70
- >= 8fbf58e17dce8f250dda9ad6b0a49b3041f0af14, < 40b4a7bb6b0b872b45f017dbf211268de098b75c
- >= 8fbf58e17dce8f250dda9ad6b0a49b3041f0af14, < af9a2bdaba0b4ceb0fc5e5122ef3fc6b7e5a366a
- >= 8fbf58e17dce8f250dda9ad6b0a49b3041f0af14, < cfec9e7f15a56cb0104bac13d01e5d11e1ba84fb
- >= 8fbf58e17dce8f250dda9ad6b0a49b3041f0af14, < 1a3670b6a6b5679fe56c5890157b344f091e64f8
- >= 8fbf58e17dce8f250dda9ad6b0a49b3041f0af14, < 4a17c73c83798c2fa9c7920ad5a98803adce3e01
- >= 8fbf58e17dce8f250dda9ad6b0a49b3041f0af14, < 8b2fd5c0aeda935294159206af9d6179282d425a
- >= 8fbf58e17dce8f250dda9ad6b0a49b3041f0af14, < 961e2a17c5e3559b3f8654d2daabdd25a42e770a
Fixed in 52fc97cbc3ba118aad84e7c001bf02ebe8496f70, 40b4a7bb6b0b872b45f017dbf211268de098b75c, af9a2bdaba0b4ceb0fc5e5122ef3fc6b7e5a366a, cfec9e7f15a56cb0104bac13d01e5d11e1ba84fb, 1a3670b6a6b5679fe56c5890157b344f091e64f8, 4a17c73c83798c2fa9c7920ad5a98803adce3e01, 8b2fd5c0aeda935294159206af9d6179282d425a, 961e2a17c5e3559b3f8654d2daabdd25a42e770a
- 5.10
Fixed in 0, 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.111, 6.18.53, 7.2.7, 7.3
Mitigation
Upgrade Linux to 52fc97cbc3ba118aad84e7c001bf02ebe8496f70 or 40b4a7bb6b0b872b45f017dbf211268de098b75c or af9a2bdaba0b4ceb0fc5e5122ef3fc6b7e5a366a or cfec9e7f15a56cb0104bac13d01e5d11e1ba84fb or 1a3670b6a6b5679fe56c5890157b344f091e64f8 or 4a17c73c83798c2fa9c7920ad5a98803adce3e01 or 8b2fd5c0aeda935294159206af9d6179282d425a or 961e2a17c5e3559b3f8654d2daabdd25a42e770a or later.
Upgrade Linux to 0 or 5.10.271 or 5.15.222 or 6.1.189 or 6.6.158 or 6.12.111 or 6.18.53 or 7.2.7 or 7.3 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.