Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2025-71067

kernel: ntfs: set dummy blocksize to read boot_block when mounting

Overview

Published
13 Jan 2026
Modified
17 Jun 2026
Low CVE
0 Registry packages
93 OS packages
7 Linux distributions
Yes Fix available
CVSS score Low, no score

Description

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]

Source: OX vulnerability database

Severity

LOW

No CVSS vector in the source. Severity comes from the advisory.

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 46 fixes

Photon OS 1 release · 1 package

fixed 1
bpftool
Photon OS fixes for CVE-2025-71067
ReleasePackageFixed in
5.0 bpftool +10 6.1.177-1.ph5

amazon linux 1 release · 3 packages

fixed 3
kernel-livepatch-6-1-168-202-320 bpftool bpftool6-12
amazon linux fixes for CVE-2025-71067
ReleasePackageFixed in
2023 kernel-livepatch-6-1-168-202-320 +1 1:1.0-0.amzn2023
2023 bpftool +20 1:6.1.168-202.320.amzn2023
2023 bpftool6-12 +20 1:6.12.64-87.122.amzn2023

debian 4 releases · 2 packages

fixed 4
linux-6-1 linux
debian fixes for CVE-2025-71067
ReleasePackageFixed in
11 linux-6-1 6.1.170-1~deb11u1
12 linux 6.1.170-1
13 linux 6.12.69-1
14 linux 6.18.3-1

echo 1 release · 1 package

fixed 1
linux
echo fixes for CVE-2025-71067
ReleasePackageFixed in
linux 1

root.io debian 2 releases · 1 package

fixed 2
linux
root.io debian fixes for CVE-2025-71067
ReleasePackageFixed in
12 linux +1 6.1.170-1
13 linux +1 6.12.69-1

root.io ubuntu 2 releases · 1 package

fixed 2
linux
root.io ubuntu fixes for CVE-2025-71067
ReleasePackageFixed in
22.04 linux +1 5.15.0-179.189.root.io.88
24.04 linux +1 6.8.0-110.110

ubuntu 2 releases · 32 packages

affected 1 fixed 32
linux linux-oracle-6-8 linux-ibm-6-8 linux-nvidia-6-8 linux-aws-6-8 linux-gcp-6-8 +26
ubuntu fixes for CVE-2025-71067
ReleasePackageFixed in
22.04 linux +16 affected
22.04 linux-oracle-6-8 6.8.0-1049.50~22.04.1
22.04 linux-ibm-6-8 6.8.0-1051.51~22.04.1
22.04 linux-nvidia-6-8 6.8.0-1051.54~22.04.1
22.04 linux-aws-6-8 6.8.0-1052.55~22.04.1
22.04 linux-gcp-6-8 6.8.0-1054.57~22.04.1

27 more rows

References

Show all 30 references

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.