CVE-2024-50202: nilfs2: propagate directory read errors from nilfs_find_entry()

Severity: medium (CVSS 5.5 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.2% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2024-11-08 · updated 2026-06-17
Weakness: CWE-755

Description

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.

Affected products

Linux kernel: from 2.6.30 before 4.19.323; from 4.20 before 5.4.285; from 5.5 before 5.10.228; from 5.11 before 5.15.169; from 5.16 before 6.1.114; from 6.2 before 6.6.58 — fixed in 4.19.323, 5.10.228, 5.15.169, 5.4.285, 6.1.114, 6.11.5

How to fix

Upgrade to a fixed version: Linux kernel 4.19.323, 5.10.228, 5.15.169, 5.4.285. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2024-50202 or the next vulnerability affects your stack