CVE-2024-50202: nilfs2: propagate directory read errors from nilfs_find_entry()
In the Linux kernel, the following vulnerability has been resolved:
nilfs2: propagate directory read errors from nilfsfindentry()
Syzbot reported that a task hang occurs in vcsopen() during a fuzzing test for nilfs2.
The root cause of this problem is that in nilfsfindentry(), which searches for directory entries, ignores errors when loading a directory page/folio via nilfsgetfolio() fails.
If the filesystem images is corrupted, and the isize of the directory inode is large, and the directory page/folio is successfully read but fails the sanity check, for example when it is zero-filled, nilfscheckfolio() may continue to spit out error messages in bursts.
Fix this issue by propagating the error to the callers when loading a page/folio fails in nilfsfindentry().
The current interface of nilfsfindentry() and its callers is outdated and cannot propagate error codes such as -EIO and -ENOMEM returned via nilfsfindentry(), so fix it together.
Other sources
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-50202?
CVE-2024-50202 has been categorized as a medium severity vulnerability.
How do I fix CVE-2024-50202?
To mitigate CVE-2024-50202, it is recommended to update the Linux kernel to the latest stable release or the patched version that resolves this issue.
Which versions of the Linux kernel are affected by CVE-2024-50202?
CVE-2024-50202 affects multiple versions of the Linux kernel between 2.6.30 and 6.12-rc3.
What is the nature of the vulnerability in CVE-2024-50202?
The vulnerability CVE-2024-50202 involves a task hang in vcs_open() due to propagated directory read errors from nilfs_find_entry().
Can CVE-2024-50202 lead to data loss?
While CVE-2024-50202 primarily causes a task hang, it may indirectly affect data operations, leading to potential data loss during the hang.