CVE-2024-38583

published 19 Jun 2024 · updated 5 Aug 2026

nilfs2: fix use-after-free of timer for log writer thread

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 2f12b2c03c5dae1a0de0a9e5853177e3d6eee3c6, Kernel 67fa90d4a2ccd9ebb0e1e168c7d0b5d0cf3c7148, Kernel 68e738be5c518fc3c4e9146b66f67c8fee0135fb and 6 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=2.6.35, >=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <2f12b2c03c5dae1a0de0a9e5853177e3d6eee3c6, >=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <67fa90d4a2ccd9ebb0e1e168c7d0b5d0cf3c7148, >=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <68e738be5c518fc3c4e9146b66f67c8fee0135fb, >=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <822ae5a8eac30478578a75f7e064f0584931bf2d, >=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <82933c84f188dcfe89eb26b0b48ab5d1ca99d164, >=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <86a30d6302deddb9fb97ba6fc4b04d0e870b582a, >=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <e65ccf3a4de4f0c763d94789615b83e11f204438, >=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <f5d4e04634c9cf68bdf23de08ada0bb92e8befe7, >=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <f9186bba4ea282b07293c1c892441df3a5441cb02f12b2c03c5dae1a0de0a9e5853177e3d6eee3c6, 67fa90d4a2ccd9ebb0e1e168c7d0b5d0cf3c7148, 68e738be5c518fc3c4e9146b66f67c8fee0135fb, 822ae5a8eac30478578a75f7e064f0584931bf2d, 82933c84f188dcfe89eb26b0b48ab5d1ca99d164, 86a30d6302deddb9fb97ba6fc4b04d0e870b582a, e65ccf3a4de4f0c763d94789615b83e11f204438, f5d4e04634c9cf68bdf23de08ada0bb92e8befe7, f9186bba4ea282b07293c1c892441df3a5441cb0

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2024-38583 severity on Zeptric[![CVE-2024-38583](https://zeptric.io/badge/cve/CVE-2024-38583.svg)](https://zeptric.io/cve/CVE-2024-38583)