f2fs: embed f2fs_gc_kthread in f2fs_sb_info
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 7950e9ac638e84518fbdd5c930939ad46a1068c5 · < 23eee01c732ec8c62b05416a05f0f88129df2960| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
f2fs: embed f2fs_gc_kthread in f2fs_sb_info
Instead of allocating f2fs_gc_kthread dynamically, embed it in f2fs_sb_info. This simplifies lifetime management and prepares for fixing race conditions during teardown.
- __sbi_store - remount|shutdown - f2fs_stop_gc_thread - access sbi->gc_thread - sbi->gc_thread = NULL - access sbi->gc_thread->f2fs_gc_task
From the CVE record · Linux
A race during f2fs teardown can leave code accessing the garbage-collection thread after its pointer has been cleared. The input does not establish how an attacker could trigger the race or whether access, authentication, or user interaction is required.
Engineers running Linux kernels with f2fs should check their kernel version; affected versions are not specified.