CVE-2025-38626 json
f2fs: fix to trigger foreground gc during f2fs_map_blocks() in lfs mode
published 2025-08-22 14 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-25575
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 6%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix to trigger foreground gc during f2fs_map_blocks() in lfs mode
w/ "mode=lfs" mount option, generic/299 will cause system panic as below:
------------[ cut here ]------------ kernel BUG at fs/f2fs/segment.c:2835! Call Trace: <TASK> f2fs_allocate_data_block+0x6f4/0xc50 f2fs_map_blocks+0x970/0x1550 f2fs_iomap_begin+0xb2/0x1e0 iomap_iter+0x1d6/0x430 __iomap_dio_rw+0x208/0x9a0 f2fs_file_write_iter+0x6b3/0xfa0 aio_write+0x15d/0x2e0 io_submit_one+0x55e/0xab0 __x64_sys_io_submit+0xa5/0x230 do_syscall_64+0x84/0x2f0 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0010:new_curseg+0x70f/0x720
The root cause of we run out-of-space is: in f2fs_map_blocks(), f2fs may trigger foreground gc only if it allocates any physical block, it will be a little bit later when there is multiple threads writing data w/ aio/dio/bufio method in parallel, since we always use OPU in lfs mode, so f2fs_map_blocks() does block allocations aggressively.
In order to fix this issue, let's give a chance to trigger foreground gc in prior to block allocation in f2fs_map_blocks().
Patch / fix
- Linux Linux 5.15.209, 6.1.167, 6.6.102, 6.12.42, 6.15.10, 6.16.1, 6.17
- linux Debian 12 6.1.170-1
- linux Debian 13 6.12.43-1
- linux Debian 14 6.16.3-1
debian advisories DEBIAN-CVE-2025-38626
- linux Ubuntu 22.04 LTS 5.15.0-186.196
- linux Ubuntu 24.04 LTS 6.8.0-100.100
- linux-aws Ubuntu 22.04 LTS 5.15.0-1112.119
- linux-aws Ubuntu 24.04 LTS 6.8.0-1046.49
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1112.122
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1047.50
- linux-gke Ubuntu 22.04 LTS 5.15.0-1108.114
- linux-gke Ubuntu 24.04 LTS 6.8.0-1043.48
ubuntu advisories UBUNTU-CVE-2025-38626
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/c737047f4665232d1e26b3620bc62df334545451 commit
- git.kernel.org/stable/c/d2f280f43a2a9d918fd23169ff3a6f3b65c7cec5 commit
- git.kernel.org/stable/c/f289690f50a01c3e085d87853392d5b7436a4cee commit
- git.kernel.org/stable/c/82765ce5c7a56f9309ee45328e763610eaf11253 commit
- git.kernel.org/stable/c/264ede8a52f18647ed5bb5f2bd9bf54f556ad8f5 commit
- git.kernel.org/stable/c/385e64a0744584397b4b52b27c96703516f39968 commit
- git.kernel.org/stable/c/1005a3ca28e90c7a64fa43023f866b960a60f791 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-38626 updated
kernel: f2fs: fix to trigger foreground gc during f2fs_map_blocks() in lfs mode
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/c737047f4665232d1e26b3620bc62df334545451
- git.kernel.org /stable/c/d2f280f43a2a9d918fd23169ff3a6f3b65c7cec5
-
git.kernel.org
/stable/c/f289690f50a01c3e085d87853392d5b7436a4cee
patch
-
git.kernel.org
/stable/c/82765ce5c7a56f9309ee45328e763610eaf11253
patch
-
git.kernel.org
/stable/c/264ede8a52f18647ed5bb5f2bd9bf54f556ad8f5
patch
-
git.kernel.org
/stable/c/385e64a0744584397b4b52b27c96703516f39968
patch
-
git.kernel.org
/stable/c/1005a3ca28e90c7a64fa43023f866b960a60f791
patch
Sources
- CVE List CVE-2025-38626
- NVD CVE-2025-38626
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.