CVE-2026-97571

Description

A flaw was found in the Linux kernel's Broadcom NetXtreme-E (bnxt_en) network driver. The driver does not properly handle memory allocation failures when configuring Transparent Packet Aggregation (TPA) buffers, leaving partially initialized ring buffers active. When memory allocation fails, an uninitialized descriptor with an invalid Direct Memory Access (DMA) address can be passed to the network device, which may trigger a system crash and lead to a Denial of Service (DoS).

Statement

A flaw was found in the Linux kernel's Broadcom NetXtreme-E (bnxt_en) network driver, rated Moderate by Red Hat Product Security. bnxt_queue_mem_alloc() ignores the error return of bnxt_alloc_one_tpa_info_data(), so when a Transparent Packet Aggregation (TPA) buffer allocation fails with -ENOMEM, a partially initialized receive ring is still installed by bnxt_queue_start(). Because the hardware-selected aggregation ID can map to an uninitialized rx_tpa[] entry, a zero DMA address may be handed to the device, which can trigger DMA errors, device failure, or a kernel crash, resulting in denial of service. Exploiting this requires local access with privileges to (re)configure the network interface on a system equipped with affected Broadcom NetXtreme-E hardware, and it also depends on inducing a memory allocation failure, which limits practical exploitability. The vulnerable code is present in Red Hat Enterprise Linux 9 (rhel-9.8.z, rhel-9.9, rhel-9.10) and Red Hat Enterprise Linux 10 (rhel-10.2.z, rhel-10.3, rhel-10.4) kernels, in Red Hat In-Vehicle OS 2, and in OpenShift Container Platform 4.22, 4.23, 5.0, and 5.1 (RHEL CoreOS 9 based). Fixes for these streams are currently deferred because the flaw can only be triggered under memory allocation failure conditions by a privileged local user, and the residual risk is limited to denial of service on hosts using the affected bnxt_en hardware. Red Hat Enterprise Linux 6, 7, and 8, the earlier RHEL 9 and RHEL 10 minor streams, and OpenShift Container Platform 4.12 through 4.21 are not affected because the vulnerable code is not present. Red Hat assigned a CVSS 3.1 base score of 5.5 (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), reflecting the local attack vector with no impact on confidentiality or integrity.

Mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

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 Score5.5N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactHighN/AN/A

Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.