CVE-2026-99735

Description

A flaw was found in the Linux kernel's Multi-Gen Least Recently Used (MGLRU) memory management subsystem. When traversing page tables, the subsystem passed local stack copies of page-table entries rather than referencing live entries. A local user could trigger concurrent memory operations that reclaim page tables while they are being walked, leaving the kernel with stale references. This race condition may lead to a system crash, resulting in a Denial of Service (DoS), or memory corruption.

Statement

This vulnerability is evaluated as Moderate severity because exploitation requires local unprivileged access with precise timing to trigger a race condition, and the impact is confined to a denial of service (kernel crash) without enabling unauthorized data access or privilege escalation. Under standard Red Hat Enterprise Linux workloads, encountering this flaw depends on specific memory-management subsystems running concurrently with background page table operations. The narrow timing window and the absence of confidentiality or integrity loss bound the overall operational risk.

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.7N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityHighN/AN/A
Privileges RequiredLowN/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:L/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Integrity,Other

Technical Impact: Alter Execution Logic; Unexpected State

The main problem is that -- if a lock is overcome -- data could be altered in a bad state.

Frequently Asked Questions

Want to get errata notifications? Sign up here.