f2fs: avoid NULL checkpoint thread access in sysfs
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 22760e3e9cecbddc475edc91600787abf407a302, Kernel 54196bcfde998fb37009f50e0ef16498f651f0f9, Kernel 5cb33b00c8fbb6e8f1fa3d281c3036d5f7c7c41f and 3 more.
In the Linux kernel, the following vulnerability has been resolved: f2fs: avoid NULL checkpoint thread access in sysfs checkpoint_merge can be enabled even when no checkpoint merge thread is running. A read-only mount is one case: f2fs does not start f2fs_issue_ckpt there, but ckpt_thread_ioprio is still writable through sysfs. The ckpt_thread_ioprio store path updates the saved ioprio value and, when checkpoint_merge is enabled, calls set_task_ioprio() for the checkpoint thread. If cprc->f2fs_issue_ckpt is NULL, that dereferences a NULL task pointer. Protect ckpt_thread_ioprio sysfs writes with s_umount as well, so the checkpoint thread cannot disappear under the store path while updating its ioprio.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.12, >=e65920661708b7c0f3db45c9cd5d0095034ee37f <22760e3e9cecbddc475edc91600787abf407a302, >=e65920661708b7c0f3db45c9cd5d0095034ee37f <54196bcfde998fb37009f50e0ef16498f651f0f9, >=e65920661708b7c0f3db45c9cd5d0095034ee37f <5cb33b00c8fbb6e8f1fa3d281c3036d5f7c7c41f, >=e65920661708b7c0f3db45c9cd5d0095034ee37f <8f3b99c50dd0da1777994ce7c7e60d39b9f60f4b, >=e65920661708b7c0f3db45c9cd5d0095034ee37f <a6573f3ffc19542de9ebc1a2b1f930fd48ba538c, >=e65920661708b7c0f3db45c9cd5d0095034ee37f <aefcec3bebdeed2bff444378122300763325ba23 | 22760e3e9cecbddc475edc91600787abf407a302, 54196bcfde998fb37009f50e0ef16498f651f0f9, 5cb33b00c8fbb6e8f1fa3d281c3036d5f7c7c41f, 8f3b99c50dd0da1777994ce7c7e60d39b9f60f4b, a6573f3ffc19542de9ebc1a2b1f930fd48ba538c, aefcec3bebdeed2bff444378122300763325ba23 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket