CVE-2026-99637

Description

A flaw was found in the Linux kernel's OverlayFS subsystem. This vulnerability allows a local user to cause a Denial of Service (DoS) by triggering a system deadlock. When processing file permission events via the fanotify (filesystem notification) mechanism on an overlay directory, the kernel fails to inherit notification suppression flags when opening the underlying directory, resulting in an unrecoverable hang.

Statement

This vulnerability is rated as having Moderate impact because it requires local system access and specific prerequisite software configurations to trigger a denial of service. To induce the deadlock condition, an environment must actively run a filesystem monitoring service that intercepts permission events on both an OverlayFS mount and its backing filesystem. Because exploitation is limited to hanging the affected file operations or system without allowing privilege escalation or data confidentiality compromise, the overall risk to standard deployments remains constrained.

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)

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.