CVE-2024-50202

MEDIUM EPSS 13.8%
Published Nov 8, 20241y ago · Modified Jun 17, 20261w ago
5.5 CVSS 3.1
Medium
Find Similar
Published Nov 8, 2024 1y ago
Last Modified Jun 17, 2026 1w ago

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.

CVSS Details

Base Score
5.5
Exploitability
1.8
Impact
3.6
Vector string
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Attack Vector Local
Attack Complexity Low
Privileges Required Low
User Interaction None
Scope Unchanged
Confidentiality None
Integrity None
Availability High

Threat Intelligence

EPSS Exploit Probability
13.8% percentile
Exploit & Patch Status
No Known Exploit
Patch Available

Weaknesses 1

CWE-755

Affected Products 10

VendorProductVersionRange
linuxlinux_kernel*≥2.6.30  –  <4.19.323
linuxlinux_kernel*≥4.20  –  <5.4.285
linuxlinux_kernel*≥5.5  –  <5.10.228
linuxlinux_kernel*≥5.11  –  <5.15.169
linuxlinux_kernel*≥5.16  –  <6.1.114
linuxlinux_kernel*≥6.2  –  <6.6.58
linuxlinux_kernel*≥6.7  –  <6.11.5
linuxlinux_kernel6.12any
linuxlinux_kernel6.12any
linuxlinux_kernel6.12any

References 10

  • git.kernel.org https://git.kernel.org/stable/c/08cfa12adf888db98879dbd735bc741360a34168
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/270a6f9df35fa2aea01ec23770dc9b3fc9a12989
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/9698088ac7704e260f492d9c254e29ed7dd8729a
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/b4b3dc9e7e604be98a222e9f941f5e93798ca475
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/bb857ae1efd3138c653239ed1e7aef14e1242c81
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/c1d0476885d708a932980b0f28cd90d9bd71db39
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/edf8146057264191d5bfe5b91773f13d936dadd3
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/efa810b15a25531cbc2f527330947b9fe16916e7
    Patch
  • lists.debian.org https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html
  • lists.debian.org https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html

Remediation

  • git.kernel.org https://git.kernel.org/stable/c/08cfa12adf888db98879dbd735bc741360a34168
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/270a6f9df35fa2aea01ec23770dc9b3fc9a12989
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/9698088ac7704e260f492d9c254e29ed7dd8729a
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/b4b3dc9e7e604be98a222e9f941f5e93798ca475
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/bb857ae1efd3138c653239ed1e7aef14e1242c81
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/c1d0476885d708a932980b0f28cd90d9bd71db39
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/edf8146057264191d5bfe5b91773f13d936dadd3
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/efa810b15a25531cbc2f527330947b9fe16916e7
    Patch