Answer in brief
CVE-2024-41034 records a Unknown severity vulnerability in nilfs2: fix kernel bug on rename operation of broken directory. 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-41034 records a Unknown severity vulnerability in nilfs2: fix kernel bug on rename operation of broken directory. 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 <ff9767ba2cb949701e45e6e4287f8af82986b703 || >=2ba466d74ed74f073257f86e61519cb8f8f46184 <24c1c8566a9b6be51f5347be2ea76e25fc82b11e || >=2ba466d74ed74f073257f86e61519cb8f8f46184 <a9a466a69b85059b341239766a10efdd3ee68a4b || >=2ba466d74ed74f073257f86e61519cb8f8f46184 <7000b438dda9d0f41a956fc9bffed92d2eb6be0d || >=2ba466d74ed74f073257f86e61519cb8f8f46184 <1a8879c0771a68d70ee2e5e66eea34207e8c6231 || >=2ba466d74ed74f073257f86e61519cb8f8f46184 <60f61514374e4a0c3b65b08c6024dd7e26150bfd || >=2ba466d74ed74f073257f86e61519cb8f8f46184 <298cd810d7fb687c90a14d8f9fd1b8719a7cb8a5 || >=2ba466d74ed74f073257f86e61519cb8f8f46184 <a9e1ddc09ca55746079cc479aa3eb6411f0d99d4 | ff9767ba2cb949701e45e6e4287f8af82986b703, 24c1c8566a9b6be51f5347be2ea76e25fc82b11e, a9a466a69b85059b341239766a10efdd3ee68a4b, 7000b438dda9d0f41a956fc9bffed92d2eb6be0d, 1a8879c0771a68d70ee2e5e66eea34207e8c6231, 60f61514374e4a0c3b65b08c6024dd7e26150bfd, 298cd810d7fb687c90a14d8f9fd1b8719a7cb8a5, a9e1ddc09ca55746079cc479aa3eb6411f0d99d4 |
| Linux/Linuxgeneric | 2.6.30 | Not reported |
Published upstream
Jul 29, 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: fix kernel bug on rename operation of broken directory Syzbot reported that in rename directory operation on broken directory on nilfs2, __block_write_begin_int() called to prepare block write may fail BUG_ON check for access exceeding the folio/page size. This is because nilfs_dotdot(), which gets parent directory reference entry ("..") of the directory to be moved or renamed, does not check consistency enough, and may return location exceeding folio/page size for broken directories. Fix this issue by checking required directory entries ("." and "..") in the first chunk of the directory in nilfs_dotdot().
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 <ff9767ba2cb949701e45e6e4287f8af82986b703 || >=2ba466d74ed74f073257f86e61519cb8f8f46184 <24c1c8566a9b6be51f5347be2ea76e25fc82b11e || >=2ba466d74ed74f073257f86e61519cb8f8f46184 <a9a466a69b85059b341239766a10efdd3ee68a4b || >=2ba466d74ed74f073257f86e61519cb8f8f46184 <7000b438dda9d0f41a956fc9bffed92d2eb6be0d || >=2ba466d74ed74f073257f86e61519cb8f8f46184 <1a8879c0771a68d70ee2e5e66eea34207e8c6231 || >=2ba466d74ed74f073257f86e61519cb8f8f46184 <60f61514374e4a0c3b65b08c6024dd7e26150bfd || >=2ba466d74ed74f073257f86e61519cb8f8f46184 <298cd810d7fb687c90a14d8f9fd1b8719a7cb8a5 || >=2ba466d74ed74f073257f86e61519cb8f8f46184 <a9e1ddc09ca55746079cc479aa3eb6411f0d99d4 | ff9767ba2cb949701e45e6e4287f8af82986b703, 24c1c8566a9b6be51f5347be2ea76e25fc82b11e, a9a466a69b85059b341239766a10efdd3ee68a4b, 7000b438dda9d0f41a956fc9bffed92d2eb6be0d, 1a8879c0771a68d70ee2e5e66eea34207e8c6231, 60f61514374e4a0c3b65b08c6024dd7e26150bfd, 298cd810d7fb687c90a14d8f9fd1b8719a7cb8a5, a9e1ddc09ca55746079cc479aa3eb6411f0d99d4 |
| Linux/Linuxgeneric | 2.6.30 | Not reported |
Published upstream
Jul 29, 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: fix kernel bug on rename operation of broken directory Syzbot reported that in rename directory operation on broken directory on nilfs2, __block_write_begin_int() called to prepare block write may fail BUG_ON check for access exceeding the folio/page size. This is because nilfs_dotdot(), which gets parent directory reference entry ("..") of the directory to be moved or renamed, does not check consistency enough, and may return location exceeding folio/page size for broken directories. Fix this issue by checking required directory entries ("." and "..") in the first chunk of the directory in nilfs_dotdot().
Quoted source text, attributed separately from HOL analysis.