CVE-2026-99702

Description

A flaw was found in the Linux kernel's virtual memory management subsystem. A local user can bypass memory protection boundaries by exploiting a race condition during memory area splitting. When the kernel duplicates a virtual memory area (VMA) before locking it, concurrent modifications can cause memory guard markers to be omitted. Consequently, subsequent process duplication or memory page merging can discard these guard protections, potentially permitting unauthorized access to restricted memory.

Statement

This vulnerability is rated with a Moderate severity impact because exploitation requires local unprivileged execution and winning a timing-dependent race condition during memory layout operations, limiting the blast radius to process-level memory protections rather than direct kernel execution. Typical multi-user enterprise deployments with standard process isolation limit the exposure, as the condition requires specialized concurrent threading to bypass memory guard markers. The issue cannot be leveraged remotely and does not immediately grant elevated administrative privileges.

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.4N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityLowN/AN/A
Integrity ImpactLowN/AN/A
Availability ImpactNoneN/AN/A

Vector

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

Understanding the Weakness (CWE)

Integrity,Availability

Technical Impact: Modify Application Data; DoS: Instability; DoS: Crash, Exit, or Restart

When a resource is not properly locked, an attacker could modify the resource while it is being operated on by the product. This might violate the product's assumption that the resource will not change, potentially leading to unexpected behaviors.

Frequently Asked Questions

Want to get errata notifications? Sign up here.