CVE-2025-38626f2fs: fix to trigger foreground gc during f2fs_map_blocks() in lfs mode
- 5.5MediumCVSS base score
- 0.18%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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().
Timeline
ID reserved
By Linux
- 4 months later
· 4 months later
Published
- 9 months later
· 9 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.18% · top 93% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 36abef4e796d382e81a0c2d21ea5327481dd7154 – < c737047f4665232d1e26b3620bc62df334545451
- affected 36abef4e796d382e81a0c2d21ea5327481dd7154 – < d2f280f43a2a9d918fd23169ff3a6f3b65c7cec5
- affected 36abef4e796d382e81a0c2d21ea5327481dd7154 – < f289690f50a01c3e085d87853392d5b7436a4cee
- affected 36abef4e796d382e81a0c2d21ea5327481dd7154 – < 82765ce5c7a56f9309ee45328e763610eaf11253
- affected 36abef4e796d382e81a0c2d21ea5327481dd7154 – < 264ede8a52f18647ed5bb5f2bd9bf54f556ad8f5
- affected 36abef4e796d382e81a0c2d21ea5327481dd7154 – < 385e64a0744584397b4b52b27c96703516f39968
- affected 36abef4e796d382e81a0c2d21ea5327481dd7154 – < 1005a3ca28e90c7a64fa43023f866b960a60f791
- affected 4.8
- unaffected < 4.8
- unaffected 5.15.209 – ≤ 5.15.*
- unaffected 6.1.167 – ≤ 6.1.*
- unaffected 6.6.102 – ≤ 6.6.*
- unaffected 6.12.42 – ≤ 6.12.*
- unaffected 6.15.10 – ≤ 6.15.*
- unaffected 6.16.1 – ≤ 6.16.*
- unaffected 6.17 – ≤ *
References
References7
- https://git.kernel.org/stable/c/c737047f4665232d1e26b3620bc62df334545451 (opens in a new tab)
- https://git.kernel.org/stable/c/d2f280f43a2a9d918fd23169ff3a6f3b65c7cec5 (opens in a new tab)
- https://git.kernel.org/stable/c/f289690f50a01c3e085d87853392d5b7436a4cee (opens in a new tab)
- https://git.kernel.org/stable/c/82765ce5c7a56f9309ee45328e763610eaf11253 (opens in a new tab)
- https://git.kernel.org/stable/c/264ede8a52f18647ed5bb5f2bd9bf54f556ad8f5 (opens in a new tab)
- https://git.kernel.org/stable/c/385e64a0744584397b4b52b27c96703516f39968 (opens in a new tab)
- https://git.kernel.org/stable/c/1005a3ca28e90c7a64fa43023f866b960a60f791 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-25575 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-38626)Record last updated .