nilfs2: fix nilfs_empty_dir() misjudgment and long loop on I/O errors
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 2ba466d74ed74f073257f86e61519cb8f8f46184 · < d18b05eda7fa77f02114f15b02c009f28ee42346| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nilfs2: fix nilfs_empty_dir() misjudgment and long loop on I/O errors
The error handling in nilfs_empty_dir() when a directory folio/page read fails is incorrect, as in the old ext2 implementation, and if the folio/page cannot be read or nilfs_check_folio() fails, it will falsely determine the directory as empty and corrupt the file system.
In addition, since nilfs_empty_dir() does not immediately return on a failed folio/page read, but continues to loop, this can cause a long loop with I/O if i_size of the directory's inode is also corrupted, causing the log writer thread to wait and hang, as reported by syzbot.
Fix these issues by making nilfs_empty_dir() immediately return a false value (0) if it fails to get a directory folio/page.
From the CVE record · Linux
In the Linux kernel's nilfs2 filesystem, a failed directory page read or validation can cause nilfs_empty_dir() to incorrectly treat a directory as empty and corrupt the filesystem. If the directory inode's size is also corrupted, repeated I/O can hang the log writer thread. The input does not specify an attacker access requirement or user interaction.
Engineers running Linux systems that use nilfs2 should check their kernel; affected versions are not specified.