CVE-2024-50158

Description

A flaw was found in the Linux kernel's Broadcom NetXtreme-E Remote Direct Memory Access (RDMA) driver (bnxt_re). When querying hardware statistics, improper bounds checking while parsing pacing statistics allows an out-of-bounds memory write. A local attacker could exploit this vulnerability to cause a Denial of Service (DoS) via a system crash or memory corruption.

Statement

A moderate-impact flaw was found in the Linux kernel's Broadcom NetXtreme-E Remote Direct Memory Access (RDMA) driver (bnxt_re) as shipped in Red Hat Enterprise Linux 9 and Fedora. The driver exports pacing statistics only on GenP5 and P7 adapters, but while parsing those statistics the driver applies an improper bounds check based on rdev->dbr_pacing, so querying hardware statistics can trigger an out-of-bounds write past the allocated statistics buffer (observed by KASAN as a slab-out-of-bounds 8-byte write in bnxt_re_get_hw_stats). A local attacker with the privileges needed to query RDMA hardware statistics on a system using a Broadcom NetXtreme-E adapter could exploit this flaw to crash the system or corrupt kernel memory, resulting in a denial of service. Within Red Hat Enterprise Linux 9, the kernel and kernel-rt components are affected: a fix is being pursued for the rhel-9.6 stream, while the rhel-9.5.z stream was closed as Won't Do. The Fedora kernel is also affected. The kernel and kernel-rt packages in Red Hat Enterprise Linux 6, the in-support Red Hat Enterprise Linux 8 z-streams, and the Hosted OpenShift (ARO and OSD) environments are not affected, and Red Hat Enterprise Linux 7 is out of support scope. Red Hat rates this flaw Moderate severity (CVSS 6.7) rather than the Important severity assigned upstream and by NIST (7.8), because exploitation requires high privileges and an attacker cannot control the nature or location of the out-of-bounds write.

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 Score6.77.87.8
Attack VectorLocalLocalLocal
Attack ComplexityLowLowLow
Privileges RequiredHighLowLow
User InteractionNoneNoneNone
ScopeUnchangedUnchangedUnchanged
ConfidentialityHighHighHigh
Integrity ImpactHighHighHigh
Availability ImpactHighHighHigh

Vector

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

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

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

Red Hat CVSS v3 Score Explanation

Because an attacker with low privileges cannot control the nature or location of the out-of-bounds write, Red Hat assesses the Privileges Required to be Low.

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.

Confidentiality

Technical Impact: Bypass Protection Mechanism

Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.

Other

Technical Impact: Varies by Context

The read operation could produce other undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.