---
id: CVE-2025-68728
title: |-
  In the Linux kernel, the following vulnerability has been resolved:

  ntfs3: fix uninit memory after failed mi_read in mi_format_new

  Fix a KMSAN un-init bug found by syzkaller.

  ntfs_get_bh() expects a buffer from sb_getblk(), that buffe…
summary: |-
  In the Linux kernel, the following vulnerability has been resolved:

  ntfs3: fix uninit memory after failed mi_read in mi_format_new

  Fix a KMSAN un-init bug found by syzkaller.

  ntfs_get_bh() expects a buffer from sb_getblk(), that buffe…
severity: none
published: '2025-12-24'
updated: '2026-10-13'
sourceUpdated: '2026-10-13T11:10:00.203'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2025-68728'
references:
  - url: 'https://git.kernel.org/stable/c/46f2a881e5a7311d41551edb3915e4d4e8802341'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/73e6b9dacf72a1e7a4265eacca46f8f33e0997d6'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/7ce8f2028dfccb2161b905cf8ab85cdd9e93909c'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/81ffe9a265df3e41534726b852ab08792e3d374d'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/8bf729b96303bb862d7c6dc05edcf51274ae04cf'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/afb144bc8e920db43a23e996eb0a6f9bdea84341'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/c70b3abfd530c7f574bc25a5f84707e6fdf0def8'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
epss: 0.00193
epssPercentile: 0.08285
ingestedAt: '2026-10-13T11:23:51.158Z'
---

## Overview

In the Linux kernel, the following vulnerability has been resolved:

ntfs3: fix uninit memory after failed mi_read in mi_format_new

Fix a KMSAN un-init bug found by syzkaller.

ntfs_get_bh() expects a buffer from sb_getblk(), that buffer may not be
uptodate. We do not bring the buffer uptodate before setting it as
uptodate. If the buffer were to not be uptodate, it could mean adding a
buffer with un-init data to the mi record. Attempting to load that record
will trigger KMSAN.

Avoid this by setting the buffer as uptodate, if it’s not already, by
overwriting it.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.