f2fs: protect critical_task_priority updates with s_umount
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
f2fs: protect critical_task_priority updates with s_umount
The sysfs store path already takes s_umount for GC thread control entries, and ckpt_thread_ioprio is covered as well.
critical_task_priority also updates checkpoint or GC kthread scheduling state, but it is not covered by that serialization. It can race with remount or teardown paths that are stopping those threads.
Protect critical_task_priority sysfs writes with s_umount too.
From the CVE record · Linux
The f2fs critical_task_priority sysfs write path updates checkpoint or GC thread scheduling state without the serialization used by related entries. Someone able to write that sysfs entry can trigger a race if the write overlaps a remount or teardown that stops those threads; the input does not describe a further impact.
Engineers running Linux kernels with f2fs should check their vendor advisory; affected versions are not specified.