CVE-2025-40150
Last modified
CVE-2025-40150 is a vulnerability of currently unknown severity. 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".. EPSS estimates a 0.21% chance of exploitation in the next 30 days.
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".
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 40d76c393cca83938b11eb7ca8983aa3cd0ed69b, < db489778e6f2a4034c2cd26fadda2796eba24dcd; >= 9703d69d9d153bb230711d0d577454552aeb13d4, < 25d2dc669f2a7e48b335d1cb07139f2ffc9fe5df; >= 9703d69d9d153bb230711d0d577454552aeb13d4, < eec1589be36fcf7440755703e4faeee2c01e360b; >= 9703d69d9d153bb230711d0d577454552aeb13d4, < d625a2b08c089397d3a03bff13fa8645e4ec7a01; >= 6.6.33, < 6.6.130 |
| Linux | Linux | 6.9 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2025-40150?
How severe is CVE-2025-40150?
How do I fix CVE-2025-40150?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-40145In the Linux kernel, the following vulnerability has been re…
- CVE-2025-40146In the Linux kernel, the following vulnerability has been re…
- CVE-2025-40147In the Linux kernel, the following vulnerability has been re…
- CVE-2025-40148In the Linux kernel, the following vulnerability has been re…
- CVE-2025-40149In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-4015A vulnerability was found in 20120630 Novel-Plus up to 0e156…7.5
- CVE-2025-40151In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-40152In the Linux kernel, the following vulnerability has been re…
- CVE-2025-40153In the Linux kernel, the following vulnerability has been re…
- CVE-2025-40154In the Linux kernel, the following vulnerability has been re…
- CVE-2025-40155In the Linux kernel, the following vulnerability has been re…7.3
- CVE-2025-40156In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2025-40150?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
