CVE-2026-99707

Description

A flaw was found in the Linux kernel's memory management subsystem. During huge page collapse operations in khugepaged, the kernel fails to flush deferred unmappings before releasing a memory page when an operation fails. An unprivileged local attacker could exploit this flaw to retain stale address mappings in the Translation Lookaside Buffer (TLB), which caches memory translations. Accessing this freed memory could allow the attacker to achieve privilege escalation, access unauthorized data, or cause a denial of service.

Statement

This vulnerability is rated as Important because an unprivileged local user could leverage this flaw to gain root privileges, read sensitive system memory, or crash the host. In default Red Hat Enterprise Linux deployments, transparent huge page support allows local processes to initiate memory collapse operations that can leave stale address translations pointing to deallocated memory. While this flaw enables a high degree of compromise, it requires existing local access and cannot be exploited across the network, distinguishing it from a Critical vulnerability.

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 Score7.8N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityHighN/AN/A
Integrity ImpactHighN/AN/A
Availability ImpactHighN/AN/A

Vector

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

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.

Frequently Asked Questions

Want to get errata notifications? Sign up here.