CVE-2026-97572 Linux CVE debrief

Who should care

Linux kernel administrators and developers, network administrators, and security teams should review configurations and versions for exposure and verify RX ring initialization. Affected operator, platform, vulnerability-management, and security-team impact should be assessed to ensure proper mitigation and remediation. This includes verifying RX ring initialization in the bnxt_en driver and monitoring for potential DMA address issues. Linux kernel updates,

Why it matters

A vulnerability in the Linux kernel's bnxt_en driver could allow an attacker to trigger a zeroed DMA address being handed out if RX ring initialization fails. Linux kernel administrators and developers should review configurations and versions for exposure and verify RX ring initialization.

• Potential DMA address issues require verification
• RX ring initialization failures may impact network stability
• Linux kernel configurations and versions require review

Technical summary

The Linux kernel's bnxt_en driver has a vulnerability where RX ring initialization failures are not properly propagated, potentially leading to zeroed DMA addresses being handed out. This issue has been resolved by propagating the error out of bnxt_init_nic(). The vulnerability is caused by the bnxt_init_rx_rings function returning an error when bnxt_alloc_one_rx_ring fails, but this return value is discarded by bnxt_init_nic. As a result, TPA could be enabled with partially zeroed rxr->rx_tpa entries, leading to potential DMA address issues. Linux kernel administrators and developers should review configurations and versions for exposure and verify RX ring initialization.

Defensive priority

Medium

Recommended defensive actions

• Review Linux kernel configurations and versions for exposure
• Verify RX ring initialization in bnxt_en driver
• Monitor for potential DMA address issues
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but evidence is limited. The Linux kernel's bnxt_en driver is affected, but no specific versions or exploitation details are provided.

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.