CVE-2026-97573 Linux CVE debrief

Who should care

Linux kernel developers and maintainers, Linux distribution maintainers, and system administrators responsible for Linux systems using the bnxt_en driver should assess exposure and verify remediation.

Why it matters

The CVE-2026-97573 vulnerability in the Linux kernel's bnxt_en driver requires attention from Linux kernel developers, maintainers, and system administrators to prevent potential system instability or crashes. The vulnerability arises from a failure to properly handle buffer allocation failures, which can lead to the use of uninitialized DMA addresses. To mitigate this risk, it is essential to review and apply the provided patches, monitor system logs for signs of instability, and verify the Linux kernel version.

• Potential system instability or crashes due to uninitialized DMA addresses.
• Need to verify Linux kernel version and apply patches to prevent exploitation.
• Possible data corruption or loss due to improper handling of buffer allocation failures.

Technical summary

The bnxt_rx_ring_reset() function in the Linux kernel's bnxt_en driver does not properly handle buffer allocation failures. When bnxt_alloc_one_rx_ring() fails to allocate memory, the error is not propagated, leading to the use of partially allocated resources and potentially causing system instability or crashes. This issue can arise when the bnxt_alloc_one_rx_ring() function fails in bnxt_alloc_one_tpa_info_data(), returning -ENOMEM on the first failed allocation and leaving the remaining rxr->rx_tpa[] entries zeroed. As a result, when the agg_id from hardware is mapped to a SW index in rxr->rx_tpa[], an uninitialized slot can be chosen, handing a zero DMA address to the device. To address this vulnerability,

Defensive priority

High

Recommended defensive actions

• Review and apply the provided patches to ensure the bnxt_en driver handles buffer allocation failures properly.
• Monitor system logs for signs of instability or crashes related to the bnxt_en driver.
• Verify the Linux kernel version and update to a patched version if necessary.
• Perform a thorough review of system configurations and network exposure to identify potential vulnerabilities.
• Implement compensating controls, such as additional monitoring or access restrictions, for exposed systems.
• Track and document changes to the Linux kernel version and related patches.
• Review and update incident response plans to address potential exploitation of this vulnerability.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description and potential impact. However, the corpus does not establish versions, exploitation, impact, or remediation, which require verification from the supplied official sources.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.