nilfs2: propagate directory read errors from nilfs_find_entry()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 2ba466d74ed74f073257f86e61519cb8f8f46184 · < 9698088ac7704e260f492d9c254e29ed7dd8729a| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nilfs2: propagate directory read errors from nilfs_find_entry()
Syzbot reported that a task hang occurs in vcs_open() during a fuzzing test for nilfs2.
The root cause of this problem is that in nilfs_find_entry(), which searches for directory entries, ignores errors when loading a directory page/folio via nilfs_get_folio() fails.
If the filesystem images is corrupted, and the i_size 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, nilfs_check_folio() 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 nilfs_find_entry().
The current interface of nilfs_find_entry() and its callers is outdated and cannot propagate error codes such as -EIO and -ENOMEM returned via nilfs_find_entry(), so fix it together.
From the CVE record · Linux
The Linux kernel's nilfs2 directory lookup can ignore errors when loading a directory page. When processing a corrupted filesystem image with a large directory inode, this can cause repeated error messages; a task hang was reported during fuzzing. The input does not specify authentication or user-interaction requirements.
Engineers running Linux kernels with nilfs2 should check their versions; affected versions are not specified.