Review reviewHigh

CVE-2024-42105

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix inode number range checks Patch series "nilfs2: fix potential issues related to reserved inodes". This series fixes one use-after-free issue reported by syzbot, caused by nilfs2's internal inode being exposed in the namespace on a corrupted filesystem, and a couple of flaws that cause problems if the starting number of non-reserved inodes written in the on-disk super block is intentionally (or corruptly) changed from its default value. This patch (of 3): In the current implementation of nilfs2, "nilfs->ns_first_...

CVSS
7.8
EPSS
0.26%
17.6% percentile
CISA KEV
Not listed
Published
2024.07.30
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.26%
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix inode number range checks Patch series "nilfs2: fix potential issues related to reserved inodes". This series fixes one use-after-free issue reported by syzbot, caused by nilfs2's internal inode being exposed in the namespace on a corrupted filesystem, and a couple of flaws that cause problems if the starting number of non-reserved inodes written in the on-disk super block is intentionally (or corruptly) changed from its default value. This patch (of 3): In the current implementation of nilfs2, "nilfs->ns_first_...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 8a9d2191e9f43bbcd256a9a6871bd73434c83f2f < 57235c3c88bb430043728d0d02f44a4efe386476, >= 8a9d2191e9f43bbcd256a9a6871bd73434c83f2f < 08cab183a624ba71603f3754643ae11cab34dbc4, >= 8a9d2191e9f43bbcd256a9a6871bd73434c83f2f < 731011ac6c37cbe97ece229fc6daa486276052c5, >= 8a9d2191e9f43bbcd256a9a6871bd73434c83f2f < 3be4dcc8d7bea52ea41f87aa4bbf959efe7a5987, >= 8a9d2191e9f43bbcd256a9a6871bd73434c83f2f < fae1959d6ab2c52677b113935e36ab4e25df37ea, >= 8a9d2191e9f43bbcd256a9a6871bd73434c83f2f < 9194f8ca57527958bee207919458e372d638d783, >= 8a9d2191e9f43bbcd256a9a6871bd73434c83f2f < 1c91058425a01131ea30dda6cf43c67b17884d6a, >= 8a9d2191e9f43bbcd256a9a6871bd73434c83f2f < e2fec219a36e0993642844be0f345513507031f4, >= 2.6.30, < 4.19.318, >= 4.20 < 5.4.280, >= 5.5 < 5.10.222, >= 5.11 < 5.15.163, >= 5.16 < 6.1.98, >= 6.2 < 6.6.39, >= 6.7 < 6.9.9, 6.10
Fixed versions
4.19.318, 5.4.280, 5.10.222, 5.15.163, 6.1.98, 6.6.39, 6.9.9

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-416
CVE-2024-42105 — Linux Linux, linux kernel | SECUFOCUS NOW