Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
  • Support the projectPage
Back

CVE-2025-71067

ntfs: set dummy blocksize to read boot_block when mounting

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. [[email protected]: changed comment style, added return value handling]

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 4 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.20% · top 90% of all CVEs (9 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 28861e3bbd9e7ac4cd9c811aad71b4d116e27930 – < 0c9327c8abf9c8f046e45008bb43d94d8ee5c6c5
    • affected 28861e3bbd9e7ac4cd9c811aad71b4d116e27930 – < 44a38eb4f7876513db5a1bccde74de9bc4389d43
    • affected 28861e3bbd9e7ac4cd9c811aad71b4d116e27930 – < 4fff9a625da958a33191c8553a03283786f9f417
    • affected 28861e3bbd9e7ac4cd9c811aad71b4d116e27930 – < b3c151fe8f543f1a0b8b5df16ce5d97afa5ec85a
    • affected 28861e3bbd9e7ac4cd9c811aad71b4d116e27930 – < d1693a7d5a38acf6424235a6070bcf5b186a360d
  • Linux · Linux

    • affected 5.15
    • unaffected < 5.15
    • unaffected 6.1.167 – ≤ 6.1.*
    • unaffected 6.6.120 – ≤ 6.6.*
    • unaffected 6.12.64 – ≤ 6.12.*
    • unaffected 6.18.3 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-71067 badge
[![CVE-2025-71067](https://cveledger.app/badge/CVE-2025-71067.svg)](https://cveledger.app/cve/CVE-2025-71067)

Record last updated .