fs/ntfs3: prevent infinite loops caused by the next valid being the same
- 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: fs/ntfs3: prevent infinite loops caused by the next valid being the same When processing valid within the range [valid : pos), if valid cannot be retrieved correctly, for example, if the retrieved valid value is always the same, this can trigger a potential infinite loop, similar to the hung problem reported by syzbot [1]. Adding a check for the valid value within the loop body, and terminating the loop and returning -EINVAL if the value is the same as the current value, can prevent this. [1] INFO: task syz.4.21:6056 blocked for more than 143 seconds. Call Trace: rwbase_write_lock+0x14f/0x750 kernel/locking/rwbase_rt.c:244 inode_lock include/linux/fs.h:1027 [inline] ntfs_file_write_iter+0xe6/0x870 fs/ntfs3/file.c:1284
Timeline
- CVE published
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
5.15
References 7
git.kernel.org
- stable/c/50c822fcb36768f1fb356f05b02a2248ef81936d
- stable/c/6d93239b4fc479f7c0a412dd196ec0ca2672d14a
- stable/c/71c8b966ec56e13c02388c1312910588bb49be7a
- stable/c/b97e371e5d1c13d722335d46eb8bc1a22b272a0e
- stable/c/4bf3bafb8e0635ed93e3cd4156dcbcc0fb960cb4
- stable/c/a47a2bb9aa6455d5cee1045814a60c749309c92b
- stable/c/27b75ca4e51e3e4554dc85dbf1a0246c66106fd3