CVE-2025-40150
- Source
- https://cve.org/CVERecord?id=CVE-2025-40150
- Import Source
- https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2025-40150.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/CVE-2025-40150
- Downstream
- Published
- 2025-11-12T10:23:27.399Z
- Modified
- 2026-05-18T05:58:07.564215690Z
- Summary
- f2fs: fix to avoid migrating empty section
- Details
-
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 - f2fsexpandinodedata - f2fsallocatepinningsection - f2fsgcrange - dogarbagecollect w/ segno #x - writepage - f2fsallocatedatablock - newcurseg - allocate segno #x
The root cause is: fallocate on pinning file may race w/ block allocation as above, result in dogarbagecollect() 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 (SUMTYPENODE), however segno #173822 was just allocated as data type segment, so in-memory SIT shows type of segno #173822 is 0 (SUMTYPEDATA).
Change as below to fix this issue: - check whether current section is empty before gc - add sanity checks on dogarbagecollect() 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".
- Database specific
{ "cna_assigner": "Linux", "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/40xxx/CVE-2025-40150.json" }- References
-
- https://git.kernel.org/stable/c/25d2dc669f2a7e48b335d1cb07139f2ffc9fe5df
- https://git.kernel.org/stable/c/d625a2b08c089397d3a03bff13fa8645e4ec7a01
- https://git.kernel.org/stable/c/db489778e6f2a4034c2cd26fadda2796eba24dcd
- https://git.kernel.org/stable/c/eec1589be36fcf7440755703e4faeee2c01e360b
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/40xxx/CVE-2025-40150.json
- https://nvd.nist.gov/vuln/detail/CVE-2025-40150
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected packages
Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected ranges
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced40d76c393cca83938b11eb7ca8983aa3cd0ed69bFixeddb489778e6f2a4034c2cd26fadda2796eba24dcd
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced9703d69d9d153bb230711d0d577454552aeb13d4Fixed25d2dc669f2a7e48b335d1cb07139f2ffc9fe5dfFixedeec1589be36fcf7440755703e4faeee2c01e360bFixedd625a2b08c089397d3a03bff13fa8645e4ec7a01