Skip to main content
VulnerabilityPublished Updated

CVE-2026-72193: Linux kernel · ntfs3: cap RESTART_TABLE free-chain walker at rt->used

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in d313416280d41bea272f02a6034dfa88008692a0 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 17:04 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in d313416280d41bea272f02a6034dfa88008692a0, 9611f644302c07d21bc8af97e3e06a3d30064253, 8128bec895075253c779d67afdc90ae513265fca +4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ b46acd6a6a627d876898e1c84d3f84902264b445, < d313416280d41bea272f02a6034dfa88008692a0
Fixed in
  • d313416280d41bea272f02a6034dfa88008692a0
LinuxLinuxAffected
  • ≥ b46acd6a6a627d876898e1c84d3f84902264b445, < 9611f644302c07d21bc8af97e3e06a3d30064253
Fixed in
  • 9611f644302c07d21bc8af97e3e06a3d30064253
LinuxLinuxAffected
  • ≥ b46acd6a6a627d876898e1c84d3f84902264b445, < 8128bec895075253c779d67afdc90ae513265fca
Fixed in
  • 8128bec895075253c779d67afdc90ae513265fca
LinuxLinuxAffected
  • ≥ b46acd6a6a627d876898e1c84d3f84902264b445, < 7972df425687daa70d971fe6ed415e78683133dd
Fixed in
  • 7972df425687daa70d971fe6ed415e78683133dd
LinuxLinuxAffected
  • ≥ b46acd6a6a627d876898e1c84d3f84902264b445, < 29b86dbe88cbbef53bb9aaec2e279359f8c450f8
Fixed in
  • 29b86dbe88cbbef53bb9aaec2e279359f8c450f8
LinuxLinuxAffected
  • ≥ b46acd6a6a627d876898e1c84d3f84902264b445, < 7ac4c86915c24c208a0f0611b71d9676686fe756
Fixed in
  • 7ac4c86915c24c208a0f0611b71d9676686fe756

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).

References

Community reviews

Loading reviews…