Answer in brief
CVE-2024-42304 records a Unknown severity vulnerability in ext4: make sure the first directory block is not a hole. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystem (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2024-42304 records a Unknown severity vulnerability in ext4: make sure the first directory block is not a hole. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystem (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystem (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3a17ca864baffc0c6f6e8aad525aa4365775a193 <d81d7e347d1f1f48a5634607d39eb90c161c8afe || >=4e19d6b65fb4fc42e352ce9883649e049da14743 <e02f9941e8c011aa3eafa799def6a134ce06bcfa || >=4e19d6b65fb4fc42e352ce9883649e049da14743 <de2a011a13a46468a6e8259db58b1b62071fe136 || >=4e19d6b65fb4fc42e352ce9883649e049da14743 <9771e3d8365ae1dd5e8846a204cb9af14e3e656a || >=4e19d6b65fb4fc42e352ce9883649e049da14743 <b609753cbbd38f8c0affd4956c0af178348523ac || >=4e19d6b65fb4fc42e352ce9883649e049da14743 <c3893d9de8ee153baac56d127d844103488133b5 || >=4e19d6b65fb4fc42e352ce9883649e049da14743 <299bc6ffa57e04e74c6cce866d6c0741fb4897a1 || >=4e19d6b65fb4fc42e352ce9883649e049da14743 <f9ca51596bbfd0f9c386dd1c613c394c78d9e5e6 || 3f0307b0d2d8b333a6964fc4c820dc86896fd1cf || 514631c2225c1fd556c799cc1893fb27b0f48f00 || 7f1f86276515f6816a98f6ca3ef99c827d54642f || 5021b7a5bdd6bb859eb648c3da71cdd6aae1d133 || >=4.19.62 <4.19.320 || >=4.9.187 <4.10 || >=4.14.135 <4.15 || >=5.1.21 <5.2 || >=5.2.4 <5.3 | d81d7e347d1f1f48a5634607d39eb90c161c8afe, e02f9941e8c011aa3eafa799def6a134ce06bcfa, de2a011a13a46468a6e8259db58b1b62071fe136, 9771e3d8365ae1dd5e8846a204cb9af14e3e656a, b609753cbbd38f8c0affd4956c0af178348523ac, c3893d9de8ee153baac56d127d844103488133b5, 299bc6ffa57e04e74c6cce866d6c0741fb4897a1, f9ca51596bbfd0f9c386dd1c613c394c78d9e5e6, 4.19.320, 4.10, 4.15, 5.2, 5.3 |
| Linux/Linuxgeneric | 5.3 | Not reported |
| Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystemgeneric | >=0 <* | * |
Published upstream
Aug 17, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystem (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3a17ca864baffc0c6f6e8aad525aa4365775a193 <d81d7e347d1f1f48a5634607d39eb90c161c8afe || >=4e19d6b65fb4fc42e352ce9883649e049da14743 <e02f9941e8c011aa3eafa799def6a134ce06bcfa || >=4e19d6b65fb4fc42e352ce9883649e049da14743 <de2a011a13a46468a6e8259db58b1b62071fe136 || >=4e19d6b65fb4fc42e352ce9883649e049da14743 <9771e3d8365ae1dd5e8846a204cb9af14e3e656a || >=4e19d6b65fb4fc42e352ce9883649e049da14743 <b609753cbbd38f8c0affd4956c0af178348523ac || >=4e19d6b65fb4fc42e352ce9883649e049da14743 <c3893d9de8ee153baac56d127d844103488133b5 || >=4e19d6b65fb4fc42e352ce9883649e049da14743 <299bc6ffa57e04e74c6cce866d6c0741fb4897a1 || >=4e19d6b65fb4fc42e352ce9883649e049da14743 <f9ca51596bbfd0f9c386dd1c613c394c78d9e5e6 || 3f0307b0d2d8b333a6964fc4c820dc86896fd1cf || 514631c2225c1fd556c799cc1893fb27b0f48f00 || 7f1f86276515f6816a98f6ca3ef99c827d54642f || 5021b7a5bdd6bb859eb648c3da71cdd6aae1d133 || >=4.19.62 <4.19.320 || >=4.9.187 <4.10 || >=4.14.135 <4.15 || >=5.1.21 <5.2 || >=5.2.4 <5.3 | d81d7e347d1f1f48a5634607d39eb90c161c8afe, e02f9941e8c011aa3eafa799def6a134ce06bcfa, de2a011a13a46468a6e8259db58b1b62071fe136, 9771e3d8365ae1dd5e8846a204cb9af14e3e656a, b609753cbbd38f8c0affd4956c0af178348523ac, c3893d9de8ee153baac56d127d844103488133b5, 299bc6ffa57e04e74c6cce866d6c0741fb4897a1, f9ca51596bbfd0f9c386dd1c613c394c78d9e5e6, 4.19.320, 4.10, 4.15, 5.2, 5.3 |
| Linux/Linuxgeneric | 5.3 | Not reported |
| Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystemgeneric | >=0 <* | * |
Published upstream
Aug 17, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.