CVE-2026-74352

Description

A flaw was found in the Linux kernel's reserved memory management. During initialization, if the allocation of the reserved memory array fails, a global pointer may still reference the freed memory. A subsequent operation, such as looking up reserved memory, could then attempt to access this freed memory, leading to a use-after-free vulnerability. This could result in system instability or a denial of service.

Statement

A post-init use-after-free can occur in the OF reserved memory code when alloc_reserved_mem_array() fails during boot. The global reserved_mem pointer may still reference the initial reserved_mem_array stored in __initdata, while reserved_mem_count remains nonzero. After init memory is freed, later calls to exported of_reserved_mem_lookup() can dereference freed memory and may crash the kernel or return corrupted reserved memory information. For the CVSS the PR:H value is used because reliable triggering normally requires control over boot time device tree or platform configuration, or conditions that make early memblock allocation fail. The issue is not network reachable and depends on local or platform level control rather than packet traffic. Impact is at least denial of service via kernel crash. In the paranoid score, confidentiality and integrity are raised because the bug class is use-after-free in kernel memory, so stale initdata reuse could theoretically affect lookup results or memory ownership decisions.

Mitigation

Mitigation for this issue is either not available or the currently available options don't 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 Score4.1N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityHighN/AN/A
Privileges RequiredHighN/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:H/PR:H/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory

The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.

Confidentiality

Technical Impact: Read Memory

Read operations on freed memory can sometimes leak sensitive information instead of causing a crash

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.

Frequently Asked Questions

Want to get errata notifications? Sign up here.