Look up another CVE · open CVE-2025-71289 in the interactive tracker
CVE-2025-71289
fs/ntfs3: handle attr_set_size() errors when truncating files
Published 2026-05-06 (5 months ago) by the Linux kernel CNA. Subsystem fs/ntfs3. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2025-71289 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
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | vulnerable | 6.1.190-1 | No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication. |
| Debian 13trixie | fixedDSA-6355-1 · 2026-06-21 · text | 6.12.94-1 | Update the kernel and reboot. DSA-6355-1 shipped the fix on 2026-06-21, in 6.12.94-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 6.19.6-1 | Update the kernel and reboot. Fixed in 6.19.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 6.19.6-1 | Update the kernel and reboot. Fixed in 6.19.6-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
If attr_set_size() fails while truncating down, the error is silently ignored and the inode may be left in an inconsistent state.
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/ntfs3/file.c
- What this is
- NTFS3 FILESYSTEMMAINTAINERS section matched on fs/ntfs3/ · ntfs3@lists.linux.dev · Supported
- Kernel module
- ntfs3
Check it on the machine
grep -w CONFIG_NTFS3_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 ntfs3Prints 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 3 releases. It does build it in 1 release, so the answer depends on which release the machine runs.
- bookwormn
- trixiem
- forky, sidn
- n
- not enabled on any flavour - this release does not build the code
- m
- a loadable module on every flavour - check lsmod, can be blacklisted
- Build switch
- CONFIG_NTFS3_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-05-06 (5 months ago)source
- CVSS
- 7.1 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:Hsource recompute it - Attack vector
- network (AV:N)source
- EPSS
- 0.25%, higher than 15.8% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- fs/ntfs3
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 5.15 | 6.6.145 | 92300ac7ff17 |
| 5.15 | 6.12.92 | 3a718675d6af |
| 5.15 | 6.18.34 | d73dcd1520d6 |
| 5.15 | 6.19.6 | 6dfea43d1151 |
| 5.15 | 7.0 | 576248a34b92 |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DSA-6355-1 | 2026-06-21 | trixie 6.12.94-1 | tracker |
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
- An NTFS3 volume can back an NFS or ksmbd share; remote SETATTR or EndOfFile requests reach vfs_truncate(), ntfs_setattr(), ntfs_truncate(), and attr_set_size().
- AC:LAttack complexity, low
- The path has no race or victim-dependent timing, and an attacker can control file layout, truncation sizes, resource pressure, and repeated attempts to induce a shrink-side failure.
- PR:LPrivileges required, low
- NFS requires write/truncate permission, while ksmbd requires a valid session and FILE_WRITE_DATA access; an ordinary authorized share user suffices without administrative capabilities.
- UI:NUser interaction, none
- Once the NTFS3 volume is mounted and shared, the attacker can issue truncation requests without any victim action.
- S:UScope, unchanged
- The inconsistent inode and resulting filesystem availability impact remain within the host kernel and filesystem security authority.
- C:NConfidentiality impact, none
- The bug provides no memory-read primitive, and data beyond the reduced valid-data length is unmapped or zero-filled rather than disclosed.
- I:LIntegrity impact, low
- The ignored failure can desynchronize VFS size, valid-data length, allocation runs, attribute-list records, and parent metadata, causing limited persistent filesystem corruption without an arbitrary memory-write primitive.
- A:HAvailability impact, high
- The inconsistency can mark an inode bad, make files inaccessible, persist damaged NTFS metadata, or render the affected volume unusable; repeated requests can sustain the denial of service.