CVE-2026-99463

Description

A flaw was found in the Linux kernel. A race condition in the memory management subsystem during the reclaim of lazy-free transparent huge pages allows an unprivileged local attacker to trigger a use-after-free condition. By concurrently invoking memory remapping operations while pages are being reclaimed, an attacker can corrupt memory, potentially leading to privilege escalation or a denial of service (DoS) through a system crash.

Statement

This vulnerability is evaluated as an Important severity flaw because an authenticated, unprivileged local attacker can exploit this condition to achieve full system compromise or cause a kernel crash. Although exploitation is confined to local users who must execute carefully timed memory-mapping operations, transparent huge pages are enabled by default in standard Red Hat Enterprise Linux environments. As a result, any local process can trigger the vulnerable memory reclamation path, elevating the risk beyond Moderate due to the potential for privilege escalation.

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.