Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2025-38626 — kernel

🟡 CVSS 5.5 — Medium ✅ No Known Exploit NVD
5.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

f2fs: fix to trigger foreground gc during f2fs_map_blocks() in lfs mode

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().

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

Affected software

CVE-2025-38626 is recorded against 2 packages.

  • kernel (from 6.16.0 up to 6.16.1)
  • linux-kernel (from 6.16 up to 6.16.1)

Timeline and source

Published on 22 August 2025 and last revised on 12 August 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)

CVE-2025-38626 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity Medium
CVSS Score 5.5
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2025-08-22
Updated 2026-08-20
Modified 2026-08-12

Affected Packages

Software From version Fixed in
kernel 6.16.0 6.16.1
linux-kernel 6.16 6.16.1

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in kernel

CVE-2025-38626 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.