ntfs3: fix uninit memory after failed mi_read in mi_format_new
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 4342306f0f0d5ff4315a204d315c1b51b914fca5 · < 81ffe9a265df3e41534726b852ab08792e3d374d| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s ntfs3 code can add uninitialized data to a record when a buffer is not up to date. Loading that record triggers a KMSAN report. The input does not establish how an attacker could trigger this or whether authentication or user interaction is required.
Engineers running Linux kernels with ntfs3 should check whether their kernel includes the fix; affected versions are not specified.