data built 2026-10-19T13:16:53Z

Look up another CVE · open CVE-2026-72207 in the interactive tracker

CVE-2026-72207

ntfs: not change 0-byte $DATA attribute to non-resident

9.8 EPSS 0.6% AV:N

Published 2026-08-15 (2 months ago) by the Linux kernel CNA. Subsystem fs/ntfs. Debian urgency: unimportant.

What to do, per Debian release

Debian's own status for CVE-2026-72207 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source

ReleaseStatus VersionWhat this means
Debian 12bookwormnot affected6.1.190-1Nothing to do. bookworm never shipped the vulnerable code.
Debian 13trixienot affected6.12.113-1Nothing to do. trixie never shipped the vulnerable code.
Debian 14forkyfixed7.1.5-1Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed7.1.5-1Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

When ntfs_resident_attr_resize() cannot grow a resident attribute in place, it retries after converting other resident attributes to non-resident to free space in the MFT recrord. Do not select zero-length resident $DATA attributes for this conversion. fsck treats 0-byte non-resident $DATA attribute as corruptions.

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

fs/ntfs/attrib.c

What this is
NTFS FILESYSTEMMAINTAINERS section matched on fs/ntfs/ · linux-fsdevel@vger.kernel.org · Maintained
Kernel module
ntfs

Check it on the machine

grep -w CONFIG_NTFS_FS /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

lsmod | grep -w ntfs

Prints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.

Show whether Debian builds this, per release

Debian does not build this code in 1 release. It does build it in 2 releases, so the answer depends on which release the machine runs. The build rule could not be established for 1 release, so nothing is claimed about those.

  • bookwormn
  • trixie?
  • forky, sidm
n
not enabled on any flavour - this release does not build the code
?
not established - no Makefile entry for the affected file
m
a loadable module on every flavour - check lsmod, can be blacklisted

Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.

Build switch
CONFIG_NTFS_FS

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published
2026-08-15 (2 months ago)source
CVSS
9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsource recompute it
Attack vector
network (AV:N)source
EPSS
0.55%, higher than 45.0% of all CVEssource
CISA KEV
not listedthe KEV catalogue
Debian urgency
unimportantsource
Subsystem
fs/ntfs

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

IntroducedFixed inCommit
7.17.1.5ceb49c372501
7.17.20aad21570197

Why the CNA scored it this way

Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source

AV:NAttack vector, network
ntfs_resident_attr_resize() is reached from VFS write/truncate/fallocate paths (ntfs_attr_expand, __ntfs_attr_truncate_vfs); fs/ntfs registers ntfs_export_ops, so remote NFS or ksmbd clients writing to an exported rw NTFS share can trigger the corrupting conversion without local shell access.
AC:LAttack complexity, low
An attacker can deterministically pack an MFT record with a resident 0-byte $DATA attribute plus other resident attributes, then grow a different resident attribute to force -ENOSPC and select that $DATA for conversion; no races or victim-specific memory layout are required.
PR:NPrivileges required, none
Exploitation requires only permission to write or truncate files on a mounted NTFS volume (local user with directory write access, authenticated SMB/NFS client, or guest/anonymous write on a misconfigured export); mounting is environmental setup, not a privilege needed during the trigger.
UI:NUser interaction, none
Once an administrator has rw-mounted and optionally exported the NTFS volume (or automounted dual-boot/shared storage), the attacker drives write/truncate operations that exhaust MFT record space; no further victim clicks, opens, or cooperative actions are required beyond that standing configuration.
S:UScope, unchanged
Impact is confined to on-disk NTFS $DATA metadata corruption and subsequent filesystem operation failure within the host kernel/filesystem security authority; this is standard local or network filesystem exploitation, not a VM escape or cross-authority sandbox breakout.
C:HConfidentiality impact, high
Converting a 0-byte resident $DATA to non-resident writes structurally invalid on-disk metadata that ntfsck/fsck treat as corruption; subsequent attribute lookups and data reads on the affected inode parse attacker-influenced corrupt non-resident layout and may read beyond intended attribute bounds.
I:HIntegrity impact, high
The bug persistently corrupts MFT $DATA records by creating invalid 0-byte non-resident attributes, enabling attacker-steerable on-disk metadata modification beyond the intended filesystem state that repair tools flag as corruption and that can render affected files or volumes inconsistent across OSes.
A:HAvailability impact, high
Corrupt 0-byte non-resident $DATA attributes cause fsck/ntfsck failures and can leave affected files or volumes unusable on remount or when accessed from Windows or Linux; persistent on-disk corruption that blocks reliable filesystem access scores Availability High.