CVE-2024-42304
ext4: 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.
INFO
Published Date :
Aug. 17, 2024, 9:15 a.m.
Last Modified :
Oct. 7, 2025, 8:26 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | MEDIUM | [email protected] |
Solution
- Update the affected kernel packages.
- Update the affected Linux packages.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2024-42304.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2024-42304 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2024-42304
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2024-42304 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-42304 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Oct. 07, 2025
Action Type Old Value New Value Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Added CWE NVD-CWE-noinfo Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.10.3 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.44 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.11 up to (excluding) 5.15.165 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.5 up to (excluding) 5.10.224 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 6.1.103 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 4.14.135 up to (excluding) 4.15 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 4.9.187 up to (excluding) 4.10 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 4.19.62 up to (excluding) 4.19.320 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.1.21 up to (excluding) 5.2 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.2.4 up to (excluding) 5.4.282 Added Reference Type kernel.org: https://git.kernel.org/stable/c/299bc6ffa57e04e74c6cce866d6c0741fb4897a1 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/9771e3d8365ae1dd5e8846a204cb9af14e3e656a Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/b609753cbbd38f8c0affd4956c0af178348523ac Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/c3893d9de8ee153baac56d127d844103488133b5 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/d81d7e347d1f1f48a5634607d39eb90c161c8afe Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/de2a011a13a46468a6e8259db58b1b62071fe136 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/e02f9941e8c011aa3eafa799def6a134ce06bcfa Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/f9ca51596bbfd0f9c386dd1c613c394c78d9e5e6 Types: Patch -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Aug. 19, 2024
Action Type Old Value New Value Added Reference kernel.org https://git.kernel.org/stable/c/d81d7e347d1f1f48a5634607d39eb90c161c8afe [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/e02f9941e8c011aa3eafa799def6a134ce06bcfa [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/de2a011a13a46468a6e8259db58b1b62071fe136 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/9771e3d8365ae1dd5e8846a204cb9af14e3e656a [No types assigned] -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Aug. 17, 2024
Action Type Old Value New Value Added 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. Added Reference kernel.org https://git.kernel.org/stable/c/b609753cbbd38f8c0affd4956c0af178348523ac [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/c3893d9de8ee153baac56d127d844103488133b5 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/299bc6ffa57e04e74c6cce866d6c0741fb4897a1 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/f9ca51596bbfd0f9c386dd1c613c394c78d9e5e6 [No types assigned]