CVE-2024-38583: nilfs2: fix use-after-free of timer for log writer thread
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 sctimer on the nilfsscinfo structure.
The problem is that even though it is used to wake up a sleeping log writer thread, sctimer is not shut down until the nilfsscinfo structure is about to be freed, and is used regardless of the thread's lifetime.
Fix this issue by limiting the use of sctimer only while the log writer thread is alive.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.27-1 - Upgrade
Upgrade
Linux kernel (nilfs2)to a version that resolves this vulnerability.Patch nilfs2: fix use-after-free of timer for log writer thread
Event History
Frequently Asked Questions
What is the severity of CVE-2024-38583?
CVE-2024-38583 has a medium severity rating due to its potential use-after-free vulnerability.
How do I fix CVE-2024-38583?
To address CVE-2024-38583, update your Linux kernel to the fixed versions such as 5.10.223-1 or 6.12.12-1.
What systems are affected by CVE-2024-38583?
CVE-2024-38583 affects multiple versions of the Linux kernel from version 2.6.35 up to 6.9.3.
What type of vulnerability is identified in CVE-2024-38583?
CVE-2024-38583 is identified as a use-after-free vulnerability in the nilfs2 log writer functionality.
Are there any known exploits for CVE-2024-38583?
As of now, there are no publicly known exploits specifically targeting CVE-2024-38583.