https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 05:43:06 +0000 https://cve.radiocsirt.org/vuln/cve-2024-39469 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nilfs2: fix nilfs_empty_dir() misjudgment and long loop on I/O errors</p> <p>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.</p> <p>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&#39;s inode is also corrupted, causing the log writer thread to wait and hang, as reported by syzbot.</p> <p>Fix these issues by making nilfs_empty_dir() immediately return a false value (0) if it fails to get a directory folio/page.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nilfs2: fix nilfs_empty_dir() misjudgment and long loop on I/O errors</p> <p>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.</p> <p>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&#39;s inode is also corrupted, causing the log writer thread to wait and hang, as reported by syzbot.</p> <p>Fix these issues by making nilfs_empty_dir() immediately return a false value (0) if it fails to get a directory folio/page.</p> https://cve.radiocsirt.org/vuln/cve-2024-39469