CVE-2025-71067ntfs: set dummy blocksize to read boot_block when mounting
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: ntfs: set dummy blocksize to read boot_block when mounting When mounting, sb->s_blocksize is used to read the boot_block without being defined or validated. Set a dummy blocksize before attempting to read the boot_block. The issue can be triggered with the following syz reproducer: mkdirat(0xffffffffffffff9c, &(0x7f0000000080)='./file1\x00', 0x0) r4 = openat$nullb(0xffffffffffffff9c, &(0x7f0000000040), 0x121403, 0x0) ioctl$FS_IOC_SETFLAGS(r4, 0x40081271, &(0x7f0000000980)=0x4000) mount(&(0x7f0000000140)=@nullb, &(0x7f0000000040)='./cgroup\x00', &(0x7f0000000000)='ntfs3\x00', 0x2208004, 0x0) syz_clone(0x88200200, 0x0, 0x0, 0x0, 0x0, 0x0) Here, the ioctl sets the bdev block size to 16384. During mount, get_tree_bdev_flags() calls sb_set_blocksize(sb, block_size(bdev)), but since block_size(bdev) > PAGE_SIZE, sb_set_blocksize() leaves sb->s_blocksize at zero. Later, ntfs_init_from_boot() attempts to read the boot_block while sb->s_blocksize is still zero, which triggers the bug. [almaz.alexandrovich@paragon-software.com: changed comment style, added return value handling]
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Deferred
- Record last updated
- May 11, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | 28861e3bbd9e7ac4cd9c811aad71b4d116e27930 builds before 0c9327c8abf9c8f046e45008bb43d94d8ee5c6c5; 28861e3bbd9e7ac4cd9c811aad71b4d116e27930 builds before 44a38eb4f7876513db5a1bccde74de9bc4389d43; 28861e3bbd9e7ac4cd9c811aad71b4d116e27930 builds before 4fff9a625da958a33191c8553a03283786f9f417; from 28861e3bbd9e7ac4cd9c811aad71b4d116e27930 before b3c151fe8f543f1a0b8b5df16ce5d97afa5ec85a; from 28861e3bbd9e7ac4cd9c811aad71b4d116e27930 before d1693a7d5a38acf6424235a6070bcf5b186a360d | CNA record |
References
- https://git.kernel.org/stable/c/0c9327c8abf9c8f046e45008bb43d94d8ee5c6c5
- https://git.kernel.org/stable/c/44a38eb4f7876513db5a1bccde74de9bc4389d43
- https://git.kernel.org/stable/c/4fff9a625da958a33191c8553a03283786f9f417
- https://git.kernel.org/stable/c/b3c151fe8f543f1a0b8b5df16ce5d97afa5ec85a
- https://git.kernel.org/stable/c/d1693a7d5a38acf6424235a6070bcf5b186a360d
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.