CVE-2024-50202: Linux kernel · nilfs2: propagate directory read errors from nilfs_find_entry()
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 4.4.0-1147.153 : update Linux kernel when convenient.
Data as of 28 Oct 2026, 11:13 UTC
- Patch
- Available – fixed in 4.4.0-1147.153, 4.15.0-1192.207~14.04.1, 4.4.0-272.306~14.04.1 +106
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 8 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-7276-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7277-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7288-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7289-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7291-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7288-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7289-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7293-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7294-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7295-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7289-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7305-1 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-6.11pkg:deb/ubuntu/linux-azure-6.11?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-nvidiapkg:deb/ubuntu/linux-azure-nvidia?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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.
References
- ubuntu.com/security/CVE-2024-50202 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-50202 (opens in a new tab)
- git.kernel.org/linus/08cfa12adf888db98879dbd735bc741360a34168 (opens in a new tab)
- git.kernel.org/stable/c/c1d0476885d708a932980b0f28cd90d9bd71db39 (opens in a new tab)
- git.kernel.org/stable/c/edf8146057264191d5bfe5b91773f13d936dadd3 (opens in a new tab)
- git.kernel.org/stable/c/270a6f9df35fa2aea01ec23770dc9b3fc9a12989 (opens in a new tab)
- git.kernel.org/stable/c/9698088ac7704e260f492d9c254e29ed7dd8729a (opens in a new tab)
- git.kernel.org/stable/c/efa810b15a25531cbc2f527330947b9fe16916e7 (opens in a new tab)
- git.kernel.org/stable/c/08cfa12adf888db98879dbd735bc741360a34168 (opens in a new tab)
- git.kernel.org/stable/c/bb857ae1efd3138c653239ed1e7aef14e1242c81 (opens in a new tab)
- git.kernel.org/stable/c/b4b3dc9e7e604be98a222e9f941f5e93798ca475 (opens in a new tab)
- ubuntu.com/security/notices/USN-7276-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7277-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7288-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7289-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7291-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7288-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7289-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7293-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7294-1 (opens in a new tab)