CVE-2026-99703

Description

A flaw was found in the Linux kernel. A local user could exploit a deadlock in the huge page (hugetlb) memory management subsystem to cause a Denial of Service (DoS). When remapping memory with shared page tables using the mremap system call, the kernel attempts to acquire a read lock while already holding a write lock on the same lock resource. This locking conflict leads to a deadlock, causing the affected processes or the entire system to hang.

Statement

This vulnerability is rated as Moderate severity because an attacker requires local access to trigger a deadlock condition, limiting the blast radius to a denial of service without compromising confidentiality or integrity. Exploitation relies on an authenticated local user initiating memory remapping operations on shared HugeTLB mappings. While the resulting kernel hang can render the host unresponsive and require a system reboot, the flaw cannot be triggered across the network or leveraged directly for code execution.

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 Score5.5N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/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:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Resource Consumption (CPU); DoS: Resource Consumption (Other); DoS: Crash, Exit, or Restart

Each thread of execution will "hang" and prevent tasks from completing. In some cases, CPU consumption may occur if a lock check occurs in a tight loop.

Frequently Asked Questions

Want to get errata notifications? Sign up here.