CVE-2026-97573

Description

A flaw was found in the Linux kernel's Broadcom NetXtreme-E (bnxt_en) network driver. The driver fails to verify memory allocation success during receive ring buffer resets, ignoring failure responses when memory is low. A local user or network event that triggers a reset under memory exhaustion can cause the driver to supply uninitialized Direct Memory Access (DMA) addresses to the network device, resulting in a system crash and a Denial of Service (DoS).

Statement

This vulnerability is evaluated as having a Moderate severity impact for Red Hat Enterprise Linux because exploitation requires physical or virtual systems equipped with Broadcom NetXtreme network adapters operating under acute memory pressure. Environments lacking this specific network hardware are unaffected. Additionally, triggering the failure path requires severe memory exhaustion during receive ring reconfiguration, restricting the realistic threat to a localized denial of service rather than code execution.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score7N/A8.1
Attack VectorLocalN/ANetwork
Attack ComplexityHighN/AHigh
Privileges RequiredLowN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityHighN/AHigh
Integrity ImpactHighN/AHigh
Availability ImpactHighN/AHigh

Vector

Red Hat: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

cve.org: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory; Read Application Data

When reusing a resource such as memory or a program variable, the original contents may not have been cleared before it is sent to an untrusted party.

Availability

Technical Impact: DoS: Crash, Exit, or Restart; DoS: Instability

The uninitialized resource may contain values that cause program flow to change in ways that the programmer did not intend, possibly leading to a crash.

Other

Technical Impact: Unexpected State; Varies by Context

The consequences vary depending on the type of resource and how it is used within the product.

Frequently Asked Questions

Want to get errata notifications? Sign up here.