CVE-2026-72202

Description

A flaw was found in the Linux kernel's NTFS filesystem driver. When calculating free clusters or Master File Table (MFT) records, a temporary state object is allocated on the heap. If this allocation fails, processes waiting for these counts can become unresponsive, leading to a denial of service (DoS) for the system.

Statement

This vulnerability is rated as Moderate severity for Red Hat Enterprise Linux because exploitation is confined to local users who can mount or interact with an NTFS volume and requires rare heap allocation failures, resulting only in a system hang rather than privilege escalation or data exposure. In typical enterprise deployments, NTFS storage is rarely utilized and the legacy NTFS driver is not loaded by default. Furthermore, supported Red Hat Enterprise Linux kernel releases do not incorporate the upstream code changes that introduced this issue.

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/A7.5
Attack VectorLocalN/ANetwork
Attack ComplexityLowN/ALow
Privileges RequiredLowN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/ANone
Integrity ImpactNoneN/ANone
Availability ImpactHighN/AHigh

Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

cve.org: CVSS:3.1/AV:N/AC:L/PR:N/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.