CVE-2025-68728 json
ntfs3: fix uninit memory after failed mi_read in mi_format_new
published 2025-12-24 10 mo ago modified 2026-10-13 27 d ago also EUVD-2025-205069
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 9%
- public exploits
- 0
- none known
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 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.
Patch / fix
- Linux Linux 5.15.198, 6.1.160, 6.6.120, 6.12.63, 6.17.13, 6.18.2, 6.19
- linux Debian 12 6.1.162-1
- linux Debian 13 6.12.63-1
- linux Debian 14 6.17.13-1
debian advisories DEBIAN-CVE-2025-68728
- linux Ubuntu 22.04 LTS 5.15.0-173.183
- linux Ubuntu 24.04 LTS 6.8.0-110.110
- linux Ubuntu 25.10 6.17.0-19.19
- linux-aws Ubuntu 22.04 LTS 5.15.0-1103.110
- linux-aws Ubuntu 24.04 LTS 6.8.0-1052.55
- linux-aws Ubuntu 25.10 6.17.0-1009.9
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1103.112
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1054.57
ubuntu advisories UBUNTU-CVE-2025-68728
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-40.1
- kernel-source-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-40.1
- kernel-source Linux Micro 6.1, Linux Micro 6.0 6.4.0-39.1
- kernel-default Linux Micro 6.1, Linux Micro 6.0 6.4.0-39.1
- kernel-kvmsmall Linux Micro 6.1, Linux Micro 6.0 6.4.0-39.1
- kernel-default-base Linux Micro 6.1, Linux Micro 6.0 6.4.0-39.1.21.16
- kernel-rt Real Time Module 15 SP7 6.4.0-150700.7.31.2
- kernel-syms-rt Real Time Module 15 SP7 6.4.0-150700.7.31.1
suse advisories SUSE-SU-2026:20845-1SUSE-SU-2026:20876-1SUSE-SU-2026:20477-1SUSE-SU-2026:20498-1SUSE-SU-2026:0587-1SUSE-SU-2026:0472-1
- kernel-source-longterm openSUSE Tumbleweed 6.18.16-1.1
- kernel-source openSUSE Tumbleweed 6.18.5-1.1
opensuse advisories openSUSE-SU-2026:10301-1openSUSE-SU-2026:10039-1
- git.kernel.org/stable/c/afb144bc8e920db43a23e996eb0a6f9bdea84341 commit
- git.kernel.org/stable/c/c70b3abfd530c7f574bc25a5f84707e6fdf0def8 commit
- git.kernel.org/stable/c/8bf729b96303bb862d7c6dc05edcf51274ae04cf commit
- git.kernel.org/stable/c/7ce8f2028dfccb2161b905cf8ab85cdd9e93909c commit
- git.kernel.org/stable/c/46f2a881e5a7311d41551edb3915e4d4e8802341 commit
- git.kernel.org/stable/c/81ffe9a265df3e41534726b852ab08792e3d374d commit
- git.kernel.org/stable/c/73e6b9dacf72a1e7a4265eacca46f8f33e0997d6 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-68728 updated
kernel: ntfs3: fix uninit memory after failed mi_read in mi_format_new
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/afb144bc8e920db43a23e996eb0a6f9bdea84341
- git.kernel.org /stable/c/c70b3abfd530c7f574bc25a5f84707e6fdf0def8
- git.kernel.org /stable/c/8bf729b96303bb862d7c6dc05edcf51274ae04cf
- git.kernel.org /stable/c/7ce8f2028dfccb2161b905cf8ab85cdd9e93909c
- git.kernel.org /stable/c/46f2a881e5a7311d41551edb3915e4d4e8802341
- git.kernel.org /stable/c/81ffe9a265df3e41534726b852ab08792e3d374d
- git.kernel.org /stable/c/73e6b9dacf72a1e7a4265eacca46f8f33e0997d6
Sources
- CVE List CVE-2025-68728
- NVD CVE-2025-68728
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.