CVE-2025-68728
ntfs3: fix uninit memory after failed mi_read in mi_format_new
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
5.15
References 7
git.kernel.org
- stable/c/afb144bc8e920db43a23e996eb0a6f9bdea84341
- stable/c/c70b3abfd530c7f574bc25a5f84707e6fdf0def8
- stable/c/8bf729b96303bb862d7c6dc05edcf51274ae04cf
- stable/c/7ce8f2028dfccb2161b905cf8ab85cdd9e93909c
- stable/c/46f2a881e5a7311d41551edb3915e4d4e8802341
- stable/c/81ffe9a265df3e41534726b852ab08792e3d374d
- stable/c/73e6b9dacf72a1e7a4265eacca46f8f33e0997d6