Answer in brief
CVE-2024-46781 records a Unknown severity vulnerability in nilfs2: fix missing cleanup on rollforward recovery error. 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-46781 records a Unknown severity vulnerability in nilfs2: fix missing cleanup on rollforward recovery error. 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 | >=0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b <35a9a7a7d94662146396199b0cfd95f9517cdd14 || >=0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b <da02f9eb333333b2e4f25d2a14967cff785ac82e || >=0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b <07e4dc2fe000ab008bcfe90be4324ef56b5b4355 || >=0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b <8e2d1e9d93c4ec51354229361ac3373058529ec4 || >=0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b <ca92c4bff2833cb30d493b935168d6cccd5c805d || >=0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b <9d8c3a585d564d776ee60d4aabec59b404be7403 || >=0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b <1cf1f7e8cd47244fa947d357ef1f642d91e219a3 || >=0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b <5787fcaab9eb5930f5378d6a1dd03d916d146622 | 35a9a7a7d94662146396199b0cfd95f9517cdd14, da02f9eb333333b2e4f25d2a14967cff785ac82e, 07e4dc2fe000ab008bcfe90be4324ef56b5b4355, 8e2d1e9d93c4ec51354229361ac3373058529ec4, ca92c4bff2833cb30d493b935168d6cccd5c805d, 9d8c3a585d564d776ee60d4aabec59b404be7403, 1cf1f7e8cd47244fa947d357ef1f642d91e219a3, 5787fcaab9eb5930f5378d6a1dd03d916d146622 |
| Linux/Linuxgeneric | 2.6.30 | Not reported |
Published upstream
Sep 18, 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 missing cleanup on rollforward recovery error In an error injection test of a routine for mount-time recovery, KASAN found a use-after-free bug. It turned out that if data recovery was performed using partial logs created by dsync writes, but an error occurred before starting the log writer to create a recovered checkpoint, the inodes whose data had been recovered were left in the ns_dirty_files list of the nilfs object and were not freed. Fix this issue by cleaning up inodes that have read the recovery data if the recovery routine fails midway before the log writer starts.
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 | >=0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b <35a9a7a7d94662146396199b0cfd95f9517cdd14 || >=0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b <da02f9eb333333b2e4f25d2a14967cff785ac82e || >=0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b <07e4dc2fe000ab008bcfe90be4324ef56b5b4355 || >=0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b <8e2d1e9d93c4ec51354229361ac3373058529ec4 || >=0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b <ca92c4bff2833cb30d493b935168d6cccd5c805d || >=0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b <9d8c3a585d564d776ee60d4aabec59b404be7403 || >=0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b <1cf1f7e8cd47244fa947d357ef1f642d91e219a3 || >=0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b <5787fcaab9eb5930f5378d6a1dd03d916d146622 | 35a9a7a7d94662146396199b0cfd95f9517cdd14, da02f9eb333333b2e4f25d2a14967cff785ac82e, 07e4dc2fe000ab008bcfe90be4324ef56b5b4355, 8e2d1e9d93c4ec51354229361ac3373058529ec4, ca92c4bff2833cb30d493b935168d6cccd5c805d, 9d8c3a585d564d776ee60d4aabec59b404be7403, 1cf1f7e8cd47244fa947d357ef1f642d91e219a3, 5787fcaab9eb5930f5378d6a1dd03d916d146622 |
| Linux/Linuxgeneric | 2.6.30 | Not reported |
Published upstream
Sep 18, 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 missing cleanup on rollforward recovery error In an error injection test of a routine for mount-time recovery, KASAN found a use-after-free bug. It turned out that if data recovery was performed using partial logs created by dsync writes, but an error occurred before starting the log writer to create a recovered checkpoint, the inodes whose data had been recovered were left in the ns_dirty_files list of the nilfs object and were not freed. Fix this issue by cleaning up inodes that have read the recovery data if the recovery routine fails midway before the log writer starts.
Quoted source text, attributed separately from HOL analysis.