CVE-2026-89834: Linux kernel · f2fs: fix to migrate all curseg types during free_segment_range
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in d358d2fc6be11eefde5eb1286f1c43a6d0330db6 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in d358d2fc6be11eefde5eb1286f1c43a6d0330db6, b9776094aa7118e8e5dfdcd791ffc8330c5ca408, b8ae1228c153622afa71a179c9d4dc268117e0f0 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 16 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to migrate all curseg types during free_segment_range In free_segment_range(), the curseg evacuation loop only iterates up to NR_CURSEG_PERSIST_TYPE (0..5), missing non-persistent in-memory curseg types such as CURSEG_COLD_DATA_PINNED and CURSEG_ALL_DATA_ATGC. Even though these in-memory curseg types are not saved in the on-disk checkpoint header, they still occupy active physical segments at runtime. If an active in-memory curseg happens to be allocated within the segment range being truncated during filesystem shrink, failing to evacuate it will cause subsequent writes to the curseg attempting out-of-bounds I/O on the truncated storage range. Fix this by expanding the curseg evacuation loop upper bound to NR_CURSEG_TYPE to ensure all active curseg types are safely migrated out of the target range.
References
- git.kernel.org/stable/c/d358d2fc6be11eefde5eb1286f1c43a6d0330db6 (opens in a new tab)
- git.kernel.org/stable/c/3b85edf3391f3e1f624f409a7d2d239885f567b7 (opens in a new tab)
- git.kernel.org/stable/c/b8ae1228c153622afa71a179c9d4dc268117e0f0 (opens in a new tab)
- git.kernel.org/stable/c/b9776094aa7118e8e5dfdcd791ffc8330c5ca408 (opens in a new tab)
- git.kernel.org/stable/c/8ec06f50ddd8d201bd7e55b896ae28ed9d4cb7d1 (opens in a new tab)