CVE Catalog

CVE-2026-53029

MediumCVSS 5.5
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.17%

7th percentile - higher than 7% of all known CVEs

Summary

In the Linux kernel's NTFS3 filesystem (ntfs3), a vulnerability was found involving the use of an uninitialized 'lcn' variable in the ntfs_iomap_begin() function. The issue occurs when the block length (len) is zero, causing 'lcn' to be used before initialization.

Risk Assessment

This can lead to unpredictable system behavior, including potential kernel memory information leaks or system crashes (panic). A local attacker could exploit this vulnerability for privilege escalation or system destabilization.

Recommendation

Immediately update the Linux kernel to a version containing the fix (commit that moves the zero-length check before 'lcn' usage). Monitor your distribution for the availability of the patch.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: prevent uninitialized lcn caused by zero len syzbot reported a uninit-value in ntfs_iomap_begin [1]. Since runs was not touched yet, run_lookup_entry() immediately fails and returns false, which makes the value of "*len" 0. Simultaneously, the new value and err value are also 0, causing the logic in attr_data_get_block_locked() to jump directly to ok, ultimately resulting in *lcn being triggered before it is set [1]. In ntfs_iomap_begin(), the check for a 0 value in clen is moved forward to before updating lcn to avoid this [1]. [1] BUG: KMSAN: uninit-value in ntfs_iomap_begin+0x8c0/0x1460 fs/ntfs3/inode.c:825 ntfs_iomap_begin+0x8c0/0x1460 fs/ntfs3/inode.c:825 iomap_iter+0x9b7/0x1540 fs/iomap/iter.c:110 Local variable lcn created at: ntfs_iomap_begin+0x15d/0x1460 fs/ntfs3/inode.c:786

Vulnerability data from NVD (NIST) · CISA KEV · EPSS