CVE-2026-99652

Description

A flaw was found in the Linux kernel. A local attacker could exploit this vulnerability to cause a Denial of Service (DoS) by triggering a kernel deadlock. This issue occurs because memory remapping (mremap) and userfaultfd move operations acquire shared page-table locks in conflicting orders during concurrent execution, causing operations to wait on each other indefinitely and freezing the system.

Statement

This vulnerability is rated as Moderate severity because it requires local execution privileges to trigger a kernel deadlock, resulting in a denial of service without exposing sensitive information or allowing data modification. The issue arises from lock-ordering conflicts when memory remapping operations run concurrently with userfaultfd page movements sharing page tables. On default Red Hat Enterprise Linux installations, unprivileged access to userfaultfd is disabled, limiting the attack surface to administrative users or workloads with explicit ptrace capabilities.

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.