CVE-2026-89593

Description

A flaw was found in the Linux kernel's huge page (hugetlb) subsystem. This vulnerability occurs when a huge page of memory is shared between a parent and a child process. If the parent process unmaps the huge page before the child, the system can incorrectly reduce the count of reserved huge pages. This error can lead to system instability or a denial of service, making the system unresponsive or unavailable.

Statement

A flaw was found in the Linux kernel's huge page (hugetlb) subsystem, rated LOW impact by Red Hat. Since the introduction of reservation adjustments in __unmap_hugepage_range(), when a huge page is mapped in both a parent and a child process and the parent unmaps the range first, the reservation adjustment causes the reserved huge page count to underflow until the child also unmaps the range. A local unprivileged user able to set up and unmap shared hugetlb mappings could exploit this incorrect reservation accounting to cause system instability or a denial of service; there is no confidentiality or integrity impact. Red Hat Enterprise Linux 7 and 8, earlier Red Hat Enterprise Linux 9 streams, and OpenShift Container Platform 4.12 through 4.18 are not affected because the vulnerable code is not present in their kernels. For the affected Red Hat Enterprise Linux 9 and 10 streams and OpenShift Container Platform 4.19 and later, the fix is deferred because the assessed severity does not meet the threshold for prioritizing a fix; the residual risk is limited to local denial of service through incorrect hugetlb reservation accounting. The upstream CVE record scores this flaw 7.1 (IMPORTANT, including integrity impact), while Red Hat's assessment is 5.5 (MODERATE, availability impact only), reflecting Red Hat's evaluation that only availability is affected.

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/A7.1
Attack VectorLocalN/ALocal
Attack ComplexityLowN/ALow
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/ANone
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:L/UI:N/S:U/C:N/I:H/A:H

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Instability

This weakness will generally lead to undefined behavior and therefore crashes. In the case of overflows involving loop index variables, the likelihood of infinite loops is also high.

Integrity

Technical Impact: Modify Memory

If the value in question is important to data (as opposed to flow), simple data corruption has occurred. Also, if the wrap around results in other conditions such as buffer overflows, further memory corruption may occur.

Confidentiality,Availability,Access Control

Technical Impact: Execute Unauthorized Code or Commands; Bypass Protection Mechanism

This weakness can sometimes trigger buffer overflows which can be used to execute arbitrary code. This is usually outside the scope of a program's implicit security policy.

Frequently Asked Questions

Want to get errata notifications? Sign up here.