nilfs2: fix use-after-free of timer for log writer thread
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 · < f9186bba4ea282b07293c1c892441df3a5441cb0| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The nilfs2 log writer timer can remain in use after its thread exits, creating a use-after-free risk. The input does not specify how an attacker could trigger it or whether access, authentication, or user interaction is required.
Engineers running Linux kernels with nilfs2 should check their versions; affected versions are not specified.