CVE-2025-40150f2fs: fix to avoid migrating empty section
- —Not scoredno CVSS score yet
- 0.26%Exploitation in 30 daysEPSS · top 82% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid migrating empty section It reports a bug from device w/ zufs: F2FS-fs (dm-64): Inconsistent segment (173822) type [1, 0] in SSA and SIT F2FS-fs (dm-64): Stopped filesystem due to reason: 4 Thread A Thread B - f2fs_expand_inode_data - f2fs_allocate_pinning_section - f2fs_gc_range - do_garbage_collect w/ segno #x - writepage - f2fs_allocate_data_block - new_curseg - allocate segno #x The root cause is: fallocate on pinning file may race w/ block allocation as above, result in do_garbage_collect() from fallocate() may migrate segment which is just allocated by a log, the log will update segment type in its in-memory structure, however GC will get segment type from on-disk SSA block, once segment type changes by log, we can detect such inconsistency, then shutdown filesystem. In this case, on-disk SSA shows type of segno #173822 is 1 (SUM_TYPE_NODE), however segno #173822 was just allocated as data type segment, so in-memory SIT shows type of segno #173822 is 0 (SUM_TYPE_DATA). Change as below to fix this issue: - check whether current section is empty before gc - add sanity checks on do_garbage_collect() to avoid any race case, result in migrating segment used by log. - btw, it fixes misc issue in printed logs: "SSA and SIT" -> "SIT and SSA".
Timeline
ID reserved
By Linux
- 7 months later
· 7 months later
Published
- 6 months later
· 6 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.
- EPSS (exploitation in 30 days)
- 0.26% · top 82% of all CVEs (12 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 40d76c393cca83938b11eb7ca8983aa3cd0ed69b – < db489778e6f2a4034c2cd26fadda2796eba24dcd
- affected 9703d69d9d153bb230711d0d577454552aeb13d4 – < 25d2dc669f2a7e48b335d1cb07139f2ffc9fe5df
- affected 9703d69d9d153bb230711d0d577454552aeb13d4 – < eec1589be36fcf7440755703e4faeee2c01e360b
- affected 9703d69d9d153bb230711d0d577454552aeb13d4 – < d625a2b08c089397d3a03bff13fa8645e4ec7a01
- affected 6.6.33 – < 6.6.130
- affected 6.9
- unaffected < 6.9
- unaffected 6.6.130 – ≤ 6.6.*
- unaffected 6.12.78 – ≤ 6.12.*
- unaffected 6.17.3 – ≤ 6.17.*
- unaffected 6.18 – ≤ *
References
References4
- https://git.kernel.org/stable/c/db489778e6f2a4034c2cd26fadda2796eba24dcd (opens in a new tab)
- https://git.kernel.org/stable/c/25d2dc669f2a7e48b335d1cb07139f2ffc9fe5df (opens in a new tab)
- https://git.kernel.org/stable/c/eec1589be36fcf7440755703e4faeee2c01e360b (opens in a new tab)
- https://git.kernel.org/stable/c/d625a2b08c089397d3a03bff13fa8645e4ec7a01 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-124933 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-40150)Record last updated .