Answer in brief
CVE-2024-42104 records a Unknown severity vulnerability in nilfs2: add missing check for inode numbers on directory entries. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (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-42104 records a Unknown severity vulnerability in nilfs2: add missing check for inode numbers on directory entries. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2ba466d74ed74f073257f86e61519cb8f8f46184 <c33c2b0d92aa1c2262d999b2598ad6fbd53bd479 || >=2ba466d74ed74f073257f86e61519cb8f8f46184 <07c176e7acc5579c133bb923ab21316d192d0a95 || >=2ba466d74ed74f073257f86e61519cb8f8f46184 <2f2fa9cf7c3537958a82fbe8c8595a5eb0861ad7 || >=2ba466d74ed74f073257f86e61519cb8f8f46184 <b11e8fb93ea5eefb2e4e719497ea177a58ff6131 || >=2ba466d74ed74f073257f86e61519cb8f8f46184 <1b7d549ed2c1fa202c751b69423a0d3a6bd5a180 || >=2ba466d74ed74f073257f86e61519cb8f8f46184 <3ab40870edb883b9633dc5cd55f5a2a11afa618d || >=2ba466d74ed74f073257f86e61519cb8f8f46184 <265fff1a01cdc083aeaf0d934c929db5cc64aebf || >=2ba466d74ed74f073257f86e61519cb8f8f46184 <bb76c6c274683c8570ad788f79d4b875bde0e458 | c33c2b0d92aa1c2262d999b2598ad6fbd53bd479, 07c176e7acc5579c133bb923ab21316d192d0a95, 2f2fa9cf7c3537958a82fbe8c8595a5eb0861ad7, b11e8fb93ea5eefb2e4e719497ea177a58ff6131, 1b7d549ed2c1fa202c751b69423a0d3a6bd5a180, 3ab40870edb883b9633dc5cd55f5a2a11afa618d, 265fff1a01cdc083aeaf0d934c929db5cc64aebf, bb76c6c274683c8570ad788f79d4b875bde0e458 |
| Linux/Linuxgeneric | 2.6.30 | Not reported |
Published upstream
Jul 30, 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: 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.
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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2ba466d74ed74f073257f86e61519cb8f8f46184 <c33c2b0d92aa1c2262d999b2598ad6fbd53bd479 || >=2ba466d74ed74f073257f86e61519cb8f8f46184 <07c176e7acc5579c133bb923ab21316d192d0a95 || >=2ba466d74ed74f073257f86e61519cb8f8f46184 <2f2fa9cf7c3537958a82fbe8c8595a5eb0861ad7 || >=2ba466d74ed74f073257f86e61519cb8f8f46184 <b11e8fb93ea5eefb2e4e719497ea177a58ff6131 || >=2ba466d74ed74f073257f86e61519cb8f8f46184 <1b7d549ed2c1fa202c751b69423a0d3a6bd5a180 || >=2ba466d74ed74f073257f86e61519cb8f8f46184 <3ab40870edb883b9633dc5cd55f5a2a11afa618d || >=2ba466d74ed74f073257f86e61519cb8f8f46184 <265fff1a01cdc083aeaf0d934c929db5cc64aebf || >=2ba466d74ed74f073257f86e61519cb8f8f46184 <bb76c6c274683c8570ad788f79d4b875bde0e458 | c33c2b0d92aa1c2262d999b2598ad6fbd53bd479, 07c176e7acc5579c133bb923ab21316d192d0a95, 2f2fa9cf7c3537958a82fbe8c8595a5eb0861ad7, b11e8fb93ea5eefb2e4e719497ea177a58ff6131, 1b7d549ed2c1fa202c751b69423a0d3a6bd5a180, 3ab40870edb883b9633dc5cd55f5a2a11afa618d, 265fff1a01cdc083aeaf0d934c929db5cc64aebf, bb76c6c274683c8570ad788f79d4b875bde0e458 |
| Linux/Linuxgeneric | 2.6.30 | Not reported |
Published upstream
Jul 30, 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: 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.
Quoted source text, attributed separately from HOL analysis.