Review reviewHigh

CVE-2024-42104

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: nilfs2: add missing check for inode numbers on directory entries Syzbot reported that mounting and unmounting a specific pattern of corrupted nilfs2 filesystem images causes a use-after-free of metadata file inodes, which triggers a kernel bug in lru_add_fn(). As Jan Kara pointed out, this is because the link count of a metadata file gets corrupted to 0, and nilfs_evict_inode(), which is called from iput(), tries to delete that inode (ifile inode in this case). The inconsistency occurs because directories containing the ino...

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: add missing check for inode numbers on directory entries Syzbot reported that mounting and unmounting a specific pattern of corrupted nilfs2 filesystem images causes a use-after-free of metadata file inodes, which triggers a kernel bug in lru_add_fn(). As Jan Kara pointed out, this is because the link count of a metadata file gets corrupted to 0, and nilfs_evict_inode(), which is called from iput(), tries to delete that inode (ifile inode in this case). The inconsistency occurs because directories containing the ino...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 2ba466d74ed74f073257f86e61519cb8f8f46184 < c33c2b0d92aa1c2262d999b2598ad6fbd53bd479, >= 2ba466d74ed74f073257f86e61519cb8f8f46184 < 07c176e7acc5579c133bb923ab21316d192d0a95, >= 2ba466d74ed74f073257f86e61519cb8f8f46184 < 2f2fa9cf7c3537958a82fbe8c8595a5eb0861ad7, >= 2ba466d74ed74f073257f86e61519cb8f8f46184 < b11e8fb93ea5eefb2e4e719497ea177a58ff6131, >= 2ba466d74ed74f073257f86e61519cb8f8f46184 < 1b7d549ed2c1fa202c751b69423a0d3a6bd5a180, >= 2ba466d74ed74f073257f86e61519cb8f8f46184 < 3ab40870edb883b9633dc5cd55f5a2a11afa618d, >= 2ba466d74ed74f073257f86e61519cb8f8f46184 < 265fff1a01cdc083aeaf0d934c929db5cc64aebf, >= 2ba466d74ed74f073257f86e61519cb8f8f46184 < bb76c6c274683c8570ad788f79d4b875bde0e458, >= 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
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-42104 — Linux Linux, linux kernel | SECUFOCUS NOW