CVE-2026-97573

CVE CVE-2026-97573EUVD EUVD-2026-86881Published 2026-09-25T10:21:57.000ZLast changed 2026-09-25T14:41:17.000ZCVSS 8.1

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux 5.10; 8fbf58e17dce8f250dda9ad6b0a49b3041f0af14 <8b2fd5c0aeda935294159206af9d6179282d425a; patch: 6.12.111; 8fbf58e17dce8f250dda9ad6b0a49b3041f0af14 <961e2a17c5e3559b3f8654d2daabdd25a42e770a; 8fbf58e17dce8f250dda9ad6b0a49b3041f0af14 <1a3670b6a6b5679fe56c5890157b344f091e64f8; patch: 0; patch: 7.3-rc3; patch: 7.2.7; patch: 6.18.53; 8fbf58e17dce8f250dda9ad6b0a49b3041f0af14 <4a17c73c83798c2fa9c7920ad5a98803adce3e01

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.