f2fs: fix to trigger foreground gc during f2fs_map_blocks() in lfs mode
Summary
| CVE | CVE-2025-38626 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2025-08-22 16:15:36 UTC |
| Updated | 2026-06-01 17:16:35 UTC |
| 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(). |
Risk And Classification
Primary CVSS: v3.1 5.5 MEDIUM from [email protected]
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Problem Types: NVD-CWE-noinfo
CVSS v3.1 Breakdown
Attack Vector
LocalAttack Complexity
LowPrivileges Required
LowUser Interaction
NoneScope
UnchangedConfidentiality
NoneIntegrity
NoneAvailability
HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Operating System | Linux | Linux Kernel | All | All | All | All |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 36abef4e796d382e81a0c2d21ea5327481dd7154 c737047f4665232d1e26b3620bc62df334545451 git | Not specified |
| CNA | Linux | Linux | affected 36abef4e796d382e81a0c2d21ea5327481dd7154 d2f280f43a2a9d918fd23169ff3a6f3b65c7cec5 git | Not specified |
| CNA | Linux | Linux | affected 36abef4e796d382e81a0c2d21ea5327481dd7154 f289690f50a01c3e085d87853392d5b7436a4cee git | Not specified |
| CNA | Linux | Linux | affected 36abef4e796d382e81a0c2d21ea5327481dd7154 82765ce5c7a56f9309ee45328e763610eaf11253 git | Not specified |
| CNA | Linux | Linux | affected 36abef4e796d382e81a0c2d21ea5327481dd7154 264ede8a52f18647ed5bb5f2bd9bf54f556ad8f5 git | Not specified |
| CNA | Linux | Linux | affected 36abef4e796d382e81a0c2d21ea5327481dd7154 385e64a0744584397b4b52b27c96703516f39968 git | Not specified |
| CNA | Linux | Linux | affected 36abef4e796d382e81a0c2d21ea5327481dd7154 1005a3ca28e90c7a64fa43023f866b960a60f791 git | Not specified |
| CNA | Linux | Linux | affected 4.8 | Not specified |
| CNA | Linux | Linux | unaffected 4.8 semver | Not specified |
| CNA | Linux | Linux | unaffected 5.15.209 5.15.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.167 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.102 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.42 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.15.10 6.15.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.16.1 6.16.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.17 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/264ede8a52f18647ed5bb5f2bd9bf54f556ad8f5 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/d2f280f43a2a9d918fd23169ff3a6f3b65c7cec5 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/f289690f50a01c3e085d87853392d5b7436a4cee | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/c737047f4665232d1e26b3620bc62df334545451 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/385e64a0744584397b4b52b27c96703516f39968 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/1005a3ca28e90c7a64fa43023f866b960a60f791 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/82765ce5c7a56f9309ee45328e763610eaf11253 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.