Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-42104nilfs2: add missing check for inode numbers on directory entries

Description

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 inode numbers of these metadata files that should not be visible in the namespace are read without checking. Fix this issue by treating the inode numbers of these internal files as errors in the sanity check helper when reading directory folios/pages. Also thanks to Hillf Danton and Matthew Wilcox for their initial mm-layer analysis.

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-42104, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.26% · top 82% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 2ba466d74ed74f073257f86e61519cb8f8f46184 – < c33c2b0d92aa1c2262d999b2598ad6fbd53bd479
    • affected 2ba466d74ed74f073257f86e61519cb8f8f46184 – < 07c176e7acc5579c133bb923ab21316d192d0a95
    • affected 2ba466d74ed74f073257f86e61519cb8f8f46184 – < 2f2fa9cf7c3537958a82fbe8c8595a5eb0861ad7
    • affected 2ba466d74ed74f073257f86e61519cb8f8f46184 – < b11e8fb93ea5eefb2e4e719497ea177a58ff6131
    • affected 2ba466d74ed74f073257f86e61519cb8f8f46184 – < 1b7d549ed2c1fa202c751b69423a0d3a6bd5a180
    • affected 2ba466d74ed74f073257f86e61519cb8f8f46184 – < 3ab40870edb883b9633dc5cd55f5a2a11afa618d
    • affected 2ba466d74ed74f073257f86e61519cb8f8f46184 – < 265fff1a01cdc083aeaf0d934c929db5cc64aebf
    • affected 2ba466d74ed74f073257f86e61519cb8f8f46184 – < bb76c6c274683c8570ad788f79d4b875bde0e458
  • Linux · Linux

    • affected 2.6.30
    • unaffected < 2.6.30
    • unaffected 4.19.318 – ≤ 4.19.*
    • unaffected 5.4.280 – ≤ 5.4.*
    • unaffected 5.10.222 – ≤ 5.10.*
    • unaffected 5.15.163 – ≤ 5.15.*
    • unaffected 6.1.98 – ≤ 6.1.*
    • unaffected 6.6.39 – ≤ 6.6.*
    • unaffected 6.9.9 – ≤ 6.9.*
    • unaffected 6.10 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-42104 badge
[![CVE-2024-42104](https://cveledger.app/badge/CVE-2024-42104.svg)](https://cveledger.app/cve/CVE-2024-42104)

Record last updated .