CVE-2026-72193
Received Received - Intake

Infinite Loop in Linux Kernel NTFS3 Driver

Vulnerability report for CVE-2026-72193, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-15

Last updated on: 2026-08-17

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: ntfs3: cap RESTART_TABLE free-chain walker at rt->used A crafted NTFS3 disk image triggers an in-kernel infinite loop at mount time, hanging the mounting thread and firing the soft-lockup watchdog within ~22s on multi-CPU hosts (panic with kernel.softlockup_panic=1). The bug is reachable from desktop USB auto-mount on distributions where udisks2 routes the NTFS signature to the in-tree ntfs3 driver (Arch family and an increasing fraction of Fedora / openSUSE / RHEL deployments); CAP_SYS_ADMIN-class manual mount elsewhere. check_rstbl()'s second walker iterates the free-entry singly-linked list headed by rt->first_free with no upper bound on iteration count: for (off = ff; off;) { if (off == RESTART_ENTRY_ALLOCATED) return false; off = le32_to_cpu(*(__le32 *)Add2Ptr(rt, off)); if (off > ts - sizeof(__le32)) return false; } The existing guards cover three exits: end-of-list (off == 0), the in-use marker (off == RESTART_ENTRY_ALLOCATED), and out-of-bounds (off > ts - sizeof(__le32)). None of the three prevents an in-bounds cycle. A crafted on-disk RESTART_TABLE whose free chain contains a self-loop or A->B->A cycle whose offsets satisfy: - in range [sizeof(struct RESTART_TABLE), ts - sizeof(__le32)] - (off - sizeof(struct RESTART_TABLE)) % rsize == 0 passes all existing guards and spins the mount-time thread forever. Reproduced in UML by hand-forging a 2 MB NTFS3 image whose journal RESTART_TABLE first_free = 0x18 and whose entry at offset 0x18 stores 0x18 as its next pointer; mount of the forged image with the in-tree ntfs3 driver never returns. Bound the walker by rt->used. Each entry on a legitimate free chain is unique, and the total slot count is ne = le16_to_cpu (rt->used). A traversal that visits more than ne slots is by construction malformed; reject it as a corrupt RESTART_TABLE. After this patch, mount of the forged image returns with -EINVAL and a log_replay failure message, and mkntfs-produced legitimate images mount cleanly (verified in the same UML harness).

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-15
Last Modified
2026-08-17
Generated
2026-09-04
AI Q&A
2026-08-15
EPSS Evaluated
2026-09-03
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux_kernel ntfs3 *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel's NTFS3 driver allows a crafted NTFS disk image to trigger an infinite loop during mount time. The loop occurs in the check_rstbl() function when processing a malformed RESTART_TABLE structure, causing the mounting thread to hang and trigger a soft-lockup watchdog within about 22 seconds on multi-CPU systems.

Detection Guidance

This vulnerability is triggered by mounting a crafted NTFS3 disk image, causing an infinite loop. Detection involves monitoring for system hangs during NTFS3 mount operations or checking for soft-lockup watchdog events. No direct commands detect the vulnerability itself, but you can monitor for symptoms like unresponsive mount processes or kernel logs indicating soft-lockup events.

Impact Analysis

This vulnerability can cause system hangs or crashes when mounting a malicious NTFS disk image. It may lead to denial-of-service conditions, requiring a system reboot. Systems with auto-mount enabled for USB drives are particularly at risk if the ntfs3 driver is used.

Compliance Impact

This vulnerability causes system hangs and potential denial-of-service conditions during NTFS3 disk mounting, which could disrupt availability of critical systems. For compliance standards like GDPR and HIPAA that require data availability and timely access, such disruptions may lead to violations if systems become unresponsive or fail to process requests within required timeframes.

Mitigation Strategies

Apply the Linux kernel patch that bounds the free-chain walker by rt->used. Update your kernel to a version containing the fix. Avoid mounting untrusted NTFS3 disk images until patched. If using affected distributions (e.g., Arch, Fedora, openSUSE, RHEL), ensure your kernel is updated to the latest stable release.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-72193. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart