CVE-2025-23130 [Medium] | Security Vulnerability in Linux Kernel

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

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-05-25	0.06%	0.04%	-0.02%
2	2026-02-10	0.02%	0.06%	+0.04%
3	2025-04-17	—	0.02%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-05-25

0.06%

0.04%

-0.02%

2026-02-10

0.02%

0.06%

+0.04%

2025-04-17

—

0.02%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
5.5	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

5.5

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

3.6

[email protected]

OS Trackers for CVE-2025-23130

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2025-23130 not yet assigned priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 3, open 2.	https://security-tracker.debian.org/tracker/CVE-2025-23130
`redhat`	—	—	https://access.redhat.com/security/cve/CVE-2025-23130
`suse`	medium	CVE-2025-23130 severity moderate: SUSE including 26 source package names (cluster-md-kmp-default, dlm-kmp-default, …), 266 product×package rows across 51 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Availability Extension 15 SP7, … (51 product lines)): Known Not Affected 266.	https://www.suse.com/security/cve/CVE-2025-23130/
`ubuntu`	medium	CVE-2025-23130 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1551 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 1145, ignored 168, released 129, needed 77, not-affected 28, needs-triage 2, pending 2.	https://ubuntu.com/security/CVE-2025-23130

Affected software / configurations for CVE-2025-23130

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 5.5, < 6.12.57	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.13, < 6.14.2	cpe:2.3:o:linux:linux_kernel::::::::

References for CVE-2025-23130

URL	Tags
https://git.kernel.org/stable/c/2dda0930fb79b847b4bfceb737577d0f6bc24d7d	Patch
https://git.kernel.org/stable/c/48ea8b200414ac69ea96f4c231f5c7ef1fbeffef	Patch
https://git.kernel.org/stable/c/9392862608d081a8346a3b841f862d732fce954b	Patch

URL

CVE-2025-23130 | f2fs: fix to avoid panic once fallocation fails for pinfile

Exploit prediction scoring system (EPSS) score for CVE-2025-23130

Common vulnerability scoring system (CVSS) metrics for CVE-2025-23130

Weakness enumeration for CVE-2025-23130

OS Trackers for CVE-2025-23130

Affected software / configurations for CVE-2025-23130

References for CVE-2025-23130