{"api_version":"1","generated_at":"2026-10-01T05:18:53+00:00","cve":"CVE-2026-89831","urls":{"html":"https://cve.report/CVE-2026-89831","api":"https://cve.report/api/cve/CVE-2026-89831.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-89831","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-89831"},"summary":{"title":"f2fs: protect critical_task_priority updates with s_umount","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: protect critical_task_priority updates with s_umount\n\nThe sysfs store path already takes s_umount for GC thread control\nentries, and ckpt_thread_ioprio is covered as well.\n\ncritical_task_priority also updates checkpoint or GC kthread scheduling\nstate, but it is not covered by that serialization. It can race with\nremount or teardown paths that are stopping those threads.\n\nProtect critical_task_priority sysfs writes with s_umount too.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-16 11:16:49","updated_at":"2026-09-16 11:16:49"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/bee6dfcc111b1dffdb3e13d73b7028b699fa0165","name":"https://git.kernel.org/stable/c/bee6dfcc111b1dffdb3e13d73b7028b699fa0165","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/8e4692c6c165e81b2cbb847d8da4b45a53483b33","name":"https://git.kernel.org/stable/c/8e4692c6c165e81b2cbb847d8da4b45a53483b33","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-89831","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89831","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 52190933c37a96164b271f3f30c16099d9eb8c09 bee6dfcc111b1dffdb3e13d73b7028b699fa0165 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 52190933c37a96164b271f3f30c16099d9eb8c09 8e4692c6c165e81b2cbb847d8da4b45a53483b33 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7.0","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.5 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["fs/f2fs/sysfs.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"bee6dfcc111b1dffdb3e13d73b7028b699fa0165","status":"affected","version":"52190933c37a96164b271f3f30c16099d9eb8c09","versionType":"git"},{"lessThan":"8e4692c6c165e81b2cbb847d8da4b45a53483b33","status":"affected","version":"52190933c37a96164b271f3f30c16099d9eb8c09","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["fs/f2fs/sysfs.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"7.0"},{"lessThan":"7.0","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.5","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.5","versionStartIncluding":"7.0","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc1","versionStartIncluding":"7.0","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: protect critical_task_priority updates with s_umount\n\nThe sysfs store path already takes s_umount for GC thread control\nentries, and ckpt_thread_ioprio is covered as well.\n\ncritical_task_priority also updates checkpoint or GC kthread scheduling\nstate, but it is not covered by that serialization. It can race with\nremount or teardown paths that are stopping those threads.\n\nProtect critical_task_priority sysfs writes with s_umount too."}],"providerMetadata":{"dateUpdated":"2026-09-16T10:31:03.702Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/bee6dfcc111b1dffdb3e13d73b7028b699fa0165"},{"url":"https://git.kernel.org/stable/c/8e4692c6c165e81b2cbb847d8da4b45a53483b33"}],"title":"f2fs: protect critical_task_priority updates with s_umount","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-89831","datePublished":"2026-09-16T10:31:03.702Z","dateReserved":"2026-09-11T19:38:34.769Z","dateUpdated":"2026-09-16T10:31:03.702Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-16 11:16:49","lastModifiedDate":"2026-09-16 11:16:49","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"89831","Ordinal":"1","Title":"f2fs: protect critical_task_priority updates with s_umount","CVE":"CVE-2026-89831","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"89831","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: protect critical_task_priority updates with s_umount\n\nThe sysfs store path already takes s_umount for GC thread control\nentries, and ckpt_thread_ioprio is covered as well.\n\ncritical_task_priority also updates checkpoint or GC kthread scheduling\nstate, but it is not covered by that serialization. It can race with\nremount or teardown paths that are stopping those threads.\n\nProtect critical_task_priority sysfs writes with s_umount too.","Type":"Description","Title":"f2fs: protect critical_task_priority updates with s_umount"}]}}}