CVE-2025-40150 linux linux
linux linux: no CVSS score yet. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
On this page
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
- 0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 18th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
- Published
- Modified
- NVD analysis
- Deferred: the NVD does not plan to analyze it
- Record from
- the NVD, synced
Fix and patched versions
- Linux Linux: fixed in 6.6.130
- Linux Linux: fixed in 6.12.78
- Linux Linux: fixed in 6.17.3
- Linux Linux: fixed in 6.18
- Debian, Ubuntu, Alpaquita: fixed package versions per release
Ask an AI about this CVE
Show the prompt
Explain CVE-2025-40150 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-40150?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-40150?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-40150 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Linux | from 6.6.33 before 6.6.130 |
| Linux | 6.9 and later |
Fixed in
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 6.6 | 6.6.130 |
| Linux | 6.12 | 6.12.78 |
| Linux | 6.17 | 6.17.3 |
| Linux | later releases | 6.18 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 13 | linux | 6.12.85-1 | DEBIAN-CVE-2025-40150 |
| Debian | 14 | linux | 6.17.6-1 | DEBIAN-CVE-2025-40150 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2025-40150 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2025-40150 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2025-40150 |
| Ubuntu | 22.04:LTS | linux-aws-6.8 | 6.8.0-1061.64~22.04.1 | UBUNTU-CVE-2025-40150 USN-8595-3 |
| Ubuntu | 22.04:LTS | linux-azure-6.8 | 6.8.0-1063.71~22.04.1 | UBUNTU-CVE-2025-40150 USN-8606-1 |
| Ubuntu | 22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1062.69~22.04.1 | UBUNTU-CVE-2025-40150 USN-8609-1 |
| Ubuntu | 22.04:LTS | linux-gcp-6.8 | 6.8.0-1064.72~22.04.1 | UBUNTU-CVE-2025-40150 USN-8567-1 |
| Ubuntu | 22.04:LTS | linux-hwe-6.8 | 6.8.0-136.136~22.04.1 | UBUNTU-CVE-2025-40150 USN-8619-1 |
| Ubuntu | 22.04:LTS | linux-ibm-6.8 | 6.8.0-1061.62~22.04.1 | UBUNTU-CVE-2025-40150 USN-8574-3 |
| Ubuntu | 22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-136.136.2~22.04.1 | UBUNTU-CVE-2025-40150 USN-8574-2 |
| Ubuntu | 22.04:LTS | linux-nvidia-6.8 | 6.8.0-1059.62~22.04.1 | UBUNTU-CVE-2025-40150 USN-8596-1 |
| Ubuntu | 22.04:LTS | linux-oracle-6.8 | 6.8.0-1058.61~22.04.1 | UBUNTU-CVE-2025-40150 USN-8595-1 |
| 39 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| Alpaquita | 25 | linux-lts | 6.12.80-r0 | BELL-CVE-2025-40150 |
| Alpaquita | stream | linux-lts | 6.18.35-r1 | BELL-CVE-2025-40150 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.
Red Hat
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Not affected | |
| Red Hat Enterprise Linux 6 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 8 | kernel | Not affected | |
| Red Hat Enterprise Linux 8 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 9 | kernel | Not affected | |
| Red Hat Enterprise Linux 9 | kernel-rt | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-40150.