fs/ntfs3: prevent potential lcn remains uninitialized
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
fs/ntfs3: prevent potential lcn remains uninitialized
The target VCN being sought was not found within runs[0], causing run_lookup() to return false. This causes run_lookup_entry() to return false, which in turn results in a len value of 0, and the new parameter passed to attr_data_get_block() is NULL. Collectively, these factors ultimately cause attr_data_get_block_locked() to exit prematurely without initializing lcn, thereby triggering [1].
To prevent [1], the clen check within ni_seek_data_or_hole() has been moved to occur before the lcn check.
[1] BUG: KMSAN: uninit-value in ni_seek_data_or_hole+0x24f/0x5f0 fs/ntfs3/frecord.c:2862 ni_seek_data_or_hole+0x24f/0x5f0 fs/ntfs3/frecord.c:2862 ntfs_llseek+0x22a/0x4a0 fs/ntfs3/file.c:1530 vfs_llseek fs/read_write.c:391 [inline]
From the CVE record · Linux
The Linux kernel’s ntfs3 filesystem can use an uninitialized value when seeking within a file if a target VCN is not found in the run list. This triggers a KMSAN bug report. The input does not specify attacker access requirements or whether user interaction is needed.
Engineers running Linux kernels with ntfs3 should check whether their kernel is affected; affected versions are not specified.