Answer in brief
CVE-2024-38583 records a Unknown severity vulnerability in nilfs2: fix use-after-free of timer for log writer thread. 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-38583 records a Unknown severity vulnerability in nilfs2: fix use-after-free of timer for log writer thread. 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 | >=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <822ae5a8eac30478578a75f7e064f0584931bf2d || >=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <82933c84f188dcfe89eb26b0b48ab5d1ca99d164 || >=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <67fa90d4a2ccd9ebb0e1e168c7d0b5d0cf3c7148 || >=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <e65ccf3a4de4f0c763d94789615b83e11f204438 || >=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <86a30d6302deddb9fb97ba6fc4b04d0e870b582a || >=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <f9186bba4ea282b07293c1c892441df3a5441cb0 || >=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <2f12b2c03c5dae1a0de0a9e5853177e3d6eee3c6 || >=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <68e738be5c518fc3c4e9146b66f67c8fee0135fb || >=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <f5d4e04634c9cf68bdf23de08ada0bb92e8befe7 | 822ae5a8eac30478578a75f7e064f0584931bf2d, 82933c84f188dcfe89eb26b0b48ab5d1ca99d164, 67fa90d4a2ccd9ebb0e1e168c7d0b5d0cf3c7148, e65ccf3a4de4f0c763d94789615b83e11f204438, 86a30d6302deddb9fb97ba6fc4b04d0e870b582a, f9186bba4ea282b07293c1c892441df3a5441cb0, 2f12b2c03c5dae1a0de0a9e5853177e3d6eee3c6, 68e738be5c518fc3c4e9146b66f67c8fee0135fb, f5d4e04634c9cf68bdf23de08ada0bb92e8befe7 |
| Linux/Linuxgeneric | 2.6.35 | Not reported |
Published upstream
Jun 19, 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 use-after-free of timer for log writer thread Patch series "nilfs2: fix log writer related issues". This bug fix series covers three nilfs2 log writer-related issues, including a timer use-after-free issue and potential deadlock issue on unmount, and a potential freeze issue in event synchronization found during their analysis. Details are described in each commit log. This patch (of 3): A use-after-free issue has been reported regarding the timer sc_timer on the nilfs_sc_info structure. The problem is that even though it is used to wake up a sleeping log writer thread, sc_timer is not shut down until the nilfs_sc_info structure is about to be freed, and is used regardless of the thread's lifetime. Fix this issue by limiting the use of sc_timer only while the log writer thread is alive.
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 | >=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <822ae5a8eac30478578a75f7e064f0584931bf2d || >=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <82933c84f188dcfe89eb26b0b48ab5d1ca99d164 || >=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <67fa90d4a2ccd9ebb0e1e168c7d0b5d0cf3c7148 || >=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <e65ccf3a4de4f0c763d94789615b83e11f204438 || >=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <86a30d6302deddb9fb97ba6fc4b04d0e870b582a || >=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <f9186bba4ea282b07293c1c892441df3a5441cb0 || >=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <2f12b2c03c5dae1a0de0a9e5853177e3d6eee3c6 || >=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <68e738be5c518fc3c4e9146b66f67c8fee0135fb || >=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <f5d4e04634c9cf68bdf23de08ada0bb92e8befe7 | 822ae5a8eac30478578a75f7e064f0584931bf2d, 82933c84f188dcfe89eb26b0b48ab5d1ca99d164, 67fa90d4a2ccd9ebb0e1e168c7d0b5d0cf3c7148, e65ccf3a4de4f0c763d94789615b83e11f204438, 86a30d6302deddb9fb97ba6fc4b04d0e870b582a, f9186bba4ea282b07293c1c892441df3a5441cb0, 2f12b2c03c5dae1a0de0a9e5853177e3d6eee3c6, 68e738be5c518fc3c4e9146b66f67c8fee0135fb, f5d4e04634c9cf68bdf23de08ada0bb92e8befe7 |
| Linux/Linuxgeneric | 2.6.35 | Not reported |
Published upstream
Jun 19, 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 use-after-free of timer for log writer thread Patch series "nilfs2: fix log writer related issues". This bug fix series covers three nilfs2 log writer-related issues, including a timer use-after-free issue and potential deadlock issue on unmount, and a potential freeze issue in event synchronization found during their analysis. Details are described in each commit log. This patch (of 3): A use-after-free issue has been reported regarding the timer sc_timer on the nilfs_sc_info structure. The problem is that even though it is used to wake up a sleeping log writer thread, sc_timer is not shut down until the nilfs_sc_info structure is about to be freed, and is used regardless of the thread's lifetime. Fix this issue by limiting the use of sc_timer only while the log writer thread is alive.
Quoted source text, attributed separately from HOL analysis.