CVE-2026-99728

Description

A flaw was found in the Linux kernel. A local user could cause a Denial of Service (DoS) through a race condition in the transparent huge page memory management subsystem. Due to missing lock synchronization during deferred page splitting, concurrent memory operations can corrupt internal kernel tracking lists, resulting in a system crash.

Statement

This vulnerability is rated as having a Moderate severity for Red Hat enterprise environments because exploitation requires an authenticated local user to win a tight race condition during kernel memory reclamation, limiting the attack scope strictly to denial of service. Under specific workloads involving concurrent huge page mapping and deferred splitting, an unprivileged local attacker could trigger memory list corruption to crash the operating system. Because the defect does not allow confidentiality loss or unauthorized privilege escalation beyond crashing the host, the impact does not warrant an Important rating.

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,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.