ntfs: set dummy blocksize to read boot_block when mounting
CVE-2025-71067 is fixed in 45 products on 1 platform, first by DEBIAN-CVE-2025-71067, released January 13, 2026. It is not reported as exploited. Patch Radar priority: High.
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]
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| bpftool · amzn 2023 | 1:6.1.168-202.320.amzn2023 | ALAS2023-2026-1681 | May 11, 2026 |
| bpftool-debuginfo · amzn 2023 | 1:6.1.168-202.320.amzn2023 | ALAS2023-2026-1681 | May 11, 2026 |
| bpftool6.12 · amzn 2023 | 1:6.12.64-87.122.amzn2023 | ALAS2023-2026-1423 | Feb 5, 2026 |
| bpftool6.12-debuginfo · amzn 2023 | 1:6.12.64-87.122.amzn2023 | ALAS2023-2026-1423 | Feb 5, 2026 |
| kernel · amzn 2023 | 1:6.1.168-202.320.amzn2023 | ALAS2023-2026-1681 | May 11, 2026 |
| kernel-debuginfo · amzn 2023 | 1:6.1.168-202.320.amzn2023 | ALAS2023-2026-1681 | May 11, 2026 |
| kernel-debuginfo-common-aarch64 · amzn 2023 | 1:6.1.168-202.320.amzn2023 | ALAS2023-2026-1681 | May 11, 2026 |
| kernel-debuginfo-common-x86_64 · amzn 2023 | 1:6.1.168-202.320.amzn2023 | ALAS2023-2026-1681 | May 11, 2026 |
| kernel-devel · amzn 2023 | 1:6.1.168-202.320.amzn2023 | ALAS2023-2026-1681 | May 11, 2026 |
| kernel-headers · amzn 2023 | 1:6.1.168-202.320.amzn2023 | ALAS2023-2026-1681 | May 11, 2026 |
| kernel-libbpf · amzn 2023 | 1:6.1.168-202.320.amzn2023 | ALAS2023-2026-1681 | May 11, 2026 |
| kernel-libbpf-debuginfo · amzn 2023 | 1:6.1.168-202.320.amzn2023 | ALAS2023-2026-1681 | May 11, 2026 |
| kernel-libbpf-devel · amzn 2023 | 1:6.1.168-202.320.amzn2023 | ALAS2023-2026-1681 | May 11, 2026 |
| kernel-libbpf-static · amzn 2023 | 1:6.1.168-202.320.amzn2023 | ALAS2023-2026-1681 | May 11, 2026 |
| kernel-livepatch-6.1.168-202.320 · amzn 2023 | 1:1.0-0.amzn2023 | ALAS2023-2026-1681 | May 11, 2026 |
| kernel-livepatch-6.12.64-87.122 · amzn 2023 | 1:1.0-0.amzn2023 | ALAS2023-2026-1423 | Feb 5, 2026 |
| kernel-modules-extra · amzn 2023 | 1:6.1.168-202.320.amzn2023 | ALAS2023-2026-1681 | May 11, 2026 |
| kernel-modules-extra-common · amzn 2023 | 1:6.1.168-202.320.amzn2023 | ALAS2023-2026-1681 | May 11, 2026 |
| kernel-tools · amzn 2023 | 1:6.1.168-202.320.amzn2023 | ALAS2023-2026-1681 | May 11, 2026 |
| kernel-tools-debuginfo · amzn 2023 | 1:6.1.168-202.320.amzn2023 | ALAS2023-2026-1681 | May 11, 2026 |
| kernel-tools-devel · amzn 2023 | 1:6.1.168-202.320.amzn2023 | ALAS2023-2026-1681 | May 11, 2026 |
| kernel6.12 · amzn 2023 | 1:6.12.64-87.122.amzn2023 | ALAS2023-2026-1423 | Feb 5, 2026 |
| kernel6.12-debuginfo · amzn 2023 | 1:6.12.64-87.122.amzn2023 | ALAS2023-2026-1423 | Feb 5, 2026 |
| kernel6.12-debuginfo-common-aarch64 · amzn 2023 | 1:6.12.64-87.122.amzn2023 | ALAS2023-2026-1423 | Feb 5, 2026 |
| kernel6.12-debuginfo-common-x86_64 · amzn 2023 | 1:6.12.64-87.122.amzn2023 | ALAS2023-2026-1423 | Feb 5, 2026 |
| kernel6.12-devel · amzn 2023 | 1:6.12.64-87.122.amzn2023 | ALAS2023-2026-1423 | Feb 5, 2026 |
| kernel6.12-headers · amzn 2023 | 1:6.12.64-87.122.amzn2023 | ALAS2023-2026-1423 | Feb 5, 2026 |
| kernel6.12-libbpf · amzn 2023 | 1:6.12.64-87.122.amzn2023 | ALAS2023-2026-1423 | Feb 5, 2026 |
| kernel6.12-libbpf-debuginfo · amzn 2023 | 1:6.12.64-87.122.amzn2023 | ALAS2023-2026-1423 | Feb 5, 2026 |
| kernel6.12-libbpf-devel · amzn 2023 | 1:6.12.64-87.122.amzn2023 | ALAS2023-2026-1423 | Feb 5, 2026 |
| kernel6.12-libbpf-static · amzn 2023 | 1:6.12.64-87.122.amzn2023 | ALAS2023-2026-1423 | Feb 5, 2026 |
| kernel6.12-modules-extra · amzn 2023 | 1:6.12.64-87.122.amzn2023 | ALAS2023-2026-1423 | Feb 5, 2026 |
| kernel6.12-modules-extra-common · amzn 2023 | 1:6.12.64-87.122.amzn2023 | ALAS2023-2026-1423 | Feb 5, 2026 |
| kernel6.12-tools · amzn 2023 | 1:6.12.64-87.122.amzn2023 | ALAS2023-2026-1423 | Feb 5, 2026 |
| kernel6.12-tools-debuginfo · amzn 2023 | 1:6.12.64-87.122.amzn2023 | ALAS2023-2026-1423 | Feb 5, 2026 |
| kernel6.12-tools-devel · amzn 2023 | 1:6.12.64-87.122.amzn2023 | ALAS2023-2026-1423 | Feb 5, 2026 |
| linux · Debian 12.15 (bookworm) | 6.1.170-1 | DEBIAN-CVE-2025-71067 | Jan 13, 2026 |
| linux · Debian 13.5 (trixie) | 6.12.69-1 | DEBIAN-CVE-2025-71067 | Jan 13, 2026 |
| linux · Debian 14 | 6.18.3-1 | DEBIAN-CVE-2025-71067 | Jan 13, 2026 |
| perf · amzn 2023 | 1:6.1.168-202.320.amzn2023 | ALAS2023-2026-1681 | May 11, 2026 |
| perf-debuginfo · amzn 2023 | 1:6.1.168-202.320.amzn2023 | ALAS2023-2026-1681 | May 11, 2026 |
| perf6.12 · amzn 2023 | 1:6.12.64-87.122.amzn2023 | ALAS2023-2026-1423 | Feb 5, 2026 |
| perf6.12-debuginfo · amzn 2023 | 1:6.12.64-87.122.amzn2023 | ALAS2023-2026-1423 | Feb 5, 2026 |
| python3-perf · amzn 2023 | 1:6.1.168-202.320.amzn2023 | ALAS2023-2026-1681 | May 11, 2026 |
| python3-perf-debuginfo · amzn 2023 | 1:6.1.168-202.320.amzn2023 | ALAS2023-2026-1681 | May 11, 2026 |
| python3-perf6.12 · amzn 2023 | 1:6.12.64-87.122.amzn2023 | ALAS2023-2026-1423 | Feb 5, 2026 |
| python3-perf6.12-debuginfo · amzn 2023 | 1:6.12.64-87.122.amzn2023 | ALAS2023-2026-1423 | Feb 5, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.