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-42304ext4: make sure the first directory block is not a hole

Description

In the Linux kernel, the following vulnerability has been resolved: ext4: make sure the first directory block is not a hole The syzbot constructs a directory that has no dirblock but is non-inline, i.e. the first directory block is a hole. And no errors are reported when creating files in this directory in the following flow. ext4_mknod ... ext4_add_entry // Read block 0 ext4_read_dirblock(dir, block, DIRENT) bh = ext4_bread(NULL, inode, block, 0) if (!bh && (type == INDEX || type == DIRENT_HTREE)) // The first directory block is a hole // But type == DIRENT, so no error is reported. After that, we get a directory block without '.' and '..' but with a valid dentry. This may cause some code that relies on dot or dotdot (such as make_indexed_dir()) to crash. Therefore when ext4_read_dirblock() finds that the first directory block is a hole report that the filesystem is corrupted and return an error to avoid loading corrupted data from disk causing something bad.

Timeline

  1. ID reserved

    By Linux

  2. · 18 days 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-42304, 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.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.23% · top 86% 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 3a17ca864baffc0c6f6e8aad525aa4365775a193 – < d81d7e347d1f1f48a5634607d39eb90c161c8afe
    • affected 4e19d6b65fb4fc42e352ce9883649e049da14743 – < e02f9941e8c011aa3eafa799def6a134ce06bcfa
    • affected 4e19d6b65fb4fc42e352ce9883649e049da14743 – < de2a011a13a46468a6e8259db58b1b62071fe136
    • affected 4e19d6b65fb4fc42e352ce9883649e049da14743 – < 9771e3d8365ae1dd5e8846a204cb9af14e3e656a
    • affected 4e19d6b65fb4fc42e352ce9883649e049da14743 – < b609753cbbd38f8c0affd4956c0af178348523ac
    • affected 4e19d6b65fb4fc42e352ce9883649e049da14743 – < c3893d9de8ee153baac56d127d844103488133b5
    • affected 4e19d6b65fb4fc42e352ce9883649e049da14743 – < 299bc6ffa57e04e74c6cce866d6c0741fb4897a1
    • affected 4e19d6b65fb4fc42e352ce9883649e049da14743 – < f9ca51596bbfd0f9c386dd1c613c394c78d9e5e6
    • affected 3f0307b0d2d8b333a6964fc4c820dc86896fd1cf
    • affected 514631c2225c1fd556c799cc1893fb27b0f48f00
    • affected 7f1f86276515f6816a98f6ca3ef99c827d54642f
    • affected 5021b7a5bdd6bb859eb648c3da71cdd6aae1d133
    • affected 4.19.62 – < 4.19.320
    • affected 4.9.187 – < 4.10
    • affected 4.14.135 – < 4.15
    • affected 5.1.21 – < 5.2
    • affected 5.2.4 – < 5.3
  • Linux · Linux

    • affected 5.3
    • unaffected < 5.3
    • unaffected 4.19.320 – ≤ 4.19.*
    • unaffected 5.4.282 – ≤ 5.4.*
    • unaffected 5.10.224 – ≤ 5.10.*
    • unaffected 5.15.165 – ≤ 5.15.*
    • unaffected 6.1.103 – ≤ 6.1.*
    • unaffected 6.6.44 – ≤ 6.6.*
    • unaffected 6.10.3 – ≤ 6.10.*
    • unaffected 6.11 – ≤ *

References

References11

Sources

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

Badge for a README or a ticket

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

Record last updated .