fs/ntfs3: prevent potential lcn remains uninitialized
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 57ac2831c8e0f168090d38e3de758c6a59db44db and Kernel 7ae7e98b71438c494532492cbf58fc0d7f7988bb.
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]
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =7.0, >=c61326967728392931f8a2240cb2cf4c81b523c1 <57ac2831c8e0f168090d38e3de758c6a59db44db, >=c61326967728392931f8a2240cb2cf4c81b523c1 <7ae7e98b71438c494532492cbf58fc0d7f7988bb | 57ac2831c8e0f168090d38e3de758c6a59db44db, 7ae7e98b71438c494532492cbf58fc0d7f7988bb |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket