CVE-2026-89831
f2fs: protect critical_task_priority updates with s_umount
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 7.2.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 52190933c37a96164b271f3f30c16099d9eb8c09 · fixed in bee6dfcc111b1dffdb3e13d73b7028b699fa0165; From 52190933c37a96164b271f3f30c16099d9eb8c09 · fixed in 8e4692c6c165e81b2cbb847d8da4b45a53483b33
- Linux Linux
7.0
- KernelLinux
From 7.0.0 · fixed in 7.2.5