CVE-2026-80723

Description

A flaw was found in the of: reserved_mem component of the Linux kernel. When the device tree defines more dynamic regions than the MAX_RESERVED_REGIONS array can hold, the fdt_scan_reserved_mem() function performs an out-of-bounds write. This vulnerability can lead to memory corruption, potentially impacting system stability or allowing for further exploitation.

Statement

A moderate out-of-bounds write vulnerability was found in the Linux kernel's of: reserved_mem device tree handling, affecting the kernel in Red Hat Enterprise Linux 10 and Red Hat In-Vehicle OS 2. During boot, fdt_scan_reserved_mem() saves each dynamically-placed /reserved-memory subnode into a fixed-size local array of MAX_RESERVED_REGIONS entries. If the device tree defines more dynamically-placed regions than this array can hold, the function writes past the end of the array, causing kernel memory corruption that can crash or destabilize the system during boot. Exploiting this flaw requires control over the device tree supplied to the kernel at boot time, which typically requires privileged access to the boot configuration or to the underlying hardware, so practical exposure is limited; for this reason Red Hat rates the flaw moderate (CVSS 5.5, local vector with privileges required) rather than the upstream CVEORG rating of important (8.4). Earlier Red Hat Enterprise Linux 6, 7, 8, and 9 streams and rhel-10.0.z are not affected because the vulnerable code is not present in those kernels. For the affected Red Hat Enterprise Linux 10 and Red Hat In-Vehicle OS 2 streams the fix is currently deferred to a future update; the residual risk is limited because triggering the out-of-bounds write requires an attacker-controlled device tree defining an excessive number of dynamically-placed reserved-memory regions. The upstream fix adds a bounds check that logs an error and skips the excess regions.

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/A8.4
Attack VectorLocalN/ALocal
Attack ComplexityLowN/ALow
Privileges RequiredLowN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/AHigh
Integrity ImpactNoneN/AHigh
Availability ImpactHighN/AHigh

Vector

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

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

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory; Execute Unauthorized Code or Commands

Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.

Other

Technical Impact: Unexpected State

Subsequent write operations can produce undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.