CVE-2026-93285 json
f2fs: embed f2fs_gc_kthread in f2fs_sb_info
published 2026-09-24 45 d ago modified 2026-10-30 9 d ago also EUVD-2026-86164
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
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
Patch / fix
- Linux Linux 5.10.273, 5.15.224, 6.1.191, 6.6.160, 6.12.112, 6.18.53, 7.2.5, 7.3
- linux Debian 13 6.12.113-1
- linux Debian 14 7.2.6-1
- linux-6.12 Debian 12 6.12.113-1~deb12u1
debian advisories DEBIAN-CVE-2026-93285
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1016.18
- linux-ibm Ubuntu 26.04 LTS 7.0.0-1017.17
- linux-riscv Ubuntu 26.04 LTS 7.0.0-42.42.1
- linux-oracle Ubuntu 26.04 LTS 7.0.0-1015.16
- linux-hwe-7.0 Ubuntu 24.04 LTS 7.0.0-42.42~24.04.1
- linux-oem-7.0 Ubuntu 26.04 LTS 7.0.0-1017.17
ubuntu advisories UBUNTU-CVE-2026-93285
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source openSUSE Tumbleweed 7.2.9-1.1
opensuse advisories openSUSE-SU-2026:12074-1
- git.kernel.org/stable/c/f13308f19d710c41a91421ad8a9dce5ed9f82ad0 commit
- git.kernel.org/stable/c/89c9954739c9b7aaaa1081faa53aa500b734bb93 commit
- git.kernel.org/stable/c/8592a6238d6071fa22228f151abb002db7383750 commit
- git.kernel.org/stable/c/cc004a1107e2c44cbdd2f1b1c2c85d32adc8f731 commit
- git.kernel.org/stable/c/7ee6be9ee7f9a803e0f539af26ab1154fdde48ba commit
- git.kernel.org/stable/c/23eee01c732ec8c62b05416a05f0f88129df2960 commit
- git.kernel.org/stable/c/99d14d61aa8beb6cb9a984b9fcddd45e35b24494 commit
- git.kernel.org/stable/c/3d7bca9d583793bb7d0bac0d95a24ddd2e129eed commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-93285 updated cvss 5.5
kernel: f2fs: embed f2fs_gc_kthread in f2fs_sb_info
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9not affected: vulnerable code not present
+1 more productsfewer
Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/f13308f19d710c41a91421ad8a9dce5ed9f82ad0
- git.kernel.org /stable/c/89c9954739c9b7aaaa1081faa53aa500b734bb93
- git.kernel.org /stable/c/8592a6238d6071fa22228f151abb002db7383750
- git.kernel.org /stable/c/cc004a1107e2c44cbdd2f1b1c2c85d32adc8f731
- git.kernel.org /stable/c/7ee6be9ee7f9a803e0f539af26ab1154fdde48ba
- git.kernel.org /stable/c/23eee01c732ec8c62b05416a05f0f88129df2960
- git.kernel.org /stable/c/99d14d61aa8beb6cb9a984b9fcddd45e35b24494
- git.kernel.org /stable/c/3d7bca9d583793bb7d0bac0d95a24ddd2e129eed
Sources
- CVE List CVE-2026-93285
- NVD CVE-2026-93285
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.