CVE-2025-23130: f2fs: fix to avoid panic once fallocation fails for pinfile
In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix to avoid panic once fallocation fails for pinfile
syzbot reports a f2fs bug as below:
------------[ cut here ]------------
kernel BUG at fs/f2fs/segment.c:2746!
CPU: 0 UID: 0 PID: 5323 Comm: syz.0.0 Not tainted 6.13.0-rc2-syzkaller-00018-g7cb1b4663150 #0
RIP: 0010:get_new_segment fs/f2fs/segment.c:2746 [inline]
RIP: 0010:new_curseg+0x1f52/0x1f70 fs/f2fs/segment.c:2876
Call Trace:
<TASK>
__allocate_new_segment+0x1ce/0x940 fs/f2fs/segment.c:3210
f2fs_allocate_new_section fs/f2fs/segment.c:3224 [inline]
f2fs_allocate_pinning_section+0xfa/0x4e0 fs/f2fs/segment.c:3238
f2fs_expand_inode_data+0x696/0xca0 fs/f2fs/file.c:1830
f2fs_fallocate+0x537/0xa10 fs/f2fs/file.c:1940
vfs_fallocate+0x569/0x6e0 fs/open.c:327
do_vfs_ioctl+0x258c/0x2e40 fs/ioctl.c:885
__do_sys_ioctl fs/ioctl.c:904 [inline]
__se_sys_ioctl+0x80/0x170 fs/ioctl.c:892
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
Concurrent pinfile allocation may run out of free section, result in
panic in get_new_segment(), let's expand pin_sem lock coverage to
include f2fs_gc(), so that we can make sure to reclaim enough free
space for following allocation.
In addition, do below changes to enhance error path handling:
- call f2fs_bug_on() only in non-pinfile allocation path in
get_new_segment().
- call reset_curseg_fields() to reset all fields of curseg in
new_curseg()
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel F2FS filesystem bug that can crash the kernel when space allocation for a pinned file fails. The business impact is availability: affected systems using F2FS could panic and reboot or stop serving workloads. The sources do not provide CVSS, CWE, or confirmed active exploitation.
Executive priority
Prioritize systems where F2FS supports production workloads, shared devices, or untrusted local users. Urgency is lower than remotely exploitable flaws because active exploitation is not evidenced, but kernel panic risk can still disrupt service availability.
Technical view
In F2FS, concurrent pinfile allocation can run out of free sections and reach a BUG in get_new_segment during fallocate handling. The kernel fix broadens pin_sem coverage around garbage collection and improves error-path handling in get_new_segment and new_curseg.
Likely exposure
Exposure is most relevant to Linux systems that mount and write to F2FS filesystems. Practical exposure depends on kernel version, distribution backports, whether F2FS is enabled, and whether local users or workloads can exercise file allocation paths.
Exploitation context
The source describes a syzbot-triggered kernel panic and does not cite public exploitation, weaponized exploit code, or KEV listing. Treat this as a potential local denial-of-service issue until vendor advisories provide clearer severity and attack preconditions.
Researcher notes
The record lacks CVSS, CWE, and precise exploitability details. Analysis should focus on F2FS mount presence, kernel lineage, distribution backports, and whether local file allocation operations are reachable by lower-privileged users or containerized workloads.
Mitigation direction
Update to a vendor kernel containing the referenced F2FS stable fixes.
Check Linux distribution advisories for backported fixes and supported kernel packages.
Avoid untrusted writable workloads on F2FS until patched.
Consider using non-F2FS storage for exposed multi-user workloads if patching is delayed.
Monitor for vendor severity, CVSS, and affected-version clarification.
Validation and detection
Inventory systems using mounted F2FS filesystems.
Map running kernels against vendor advisories and fixed stable commits.
Confirm patched kernels include the referenced F2FS fix commits or backports.
Review crash logs for f2fs segment BUG or fallocate-related panic signatures.
Verify rebooted systems after patching are running the updated kernel.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-23130 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
4Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Apr 16, 2025, 14:13 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.