CVE-2026-99660

Description

A flaw was found in the Linux kernel. A local user can cause a denial of service (DoS) by exploiting a race condition within the userfaultfd subsystem. When unregistering a virtual memory area (VMA), pending page faults are awakened before acquiring the necessary write lock, allowing a concurrent page fault to queue itself after the wake-up. Consequently, the waiting thread can remain asleep indefinitely, leaving the affected process hung.

Statement

This vulnerability is rated as having a Moderate severity for Red Hat enterprise environments because exploitation is confined to local authenticated users and can only lead to a denial of service through task hangs, without compromising system confidentiality or data integrity. The issue requires concurrent memory fault handling and unregistration operations against userfaultfd-managed memory regions. Exposure is further restricted in typical installations where unprivileged userfaultfd usage is disabled by default, limiting invocation to processes granted administrative debugging 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 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)

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.