CVE-2025-23130

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> f2fs: fix to avoid panic once fallocation fails for pinfile<br /> <br /> syzbot reports a f2fs bug as below:<br /> <br /> ------------[ cut here ]------------<br /> kernel BUG at fs/f2fs/segment.c:2746!<br /> CPU: 0 UID: 0 PID: 5323 Comm: syz.0.0 Not tainted 6.13.0-rc2-syzkaller-00018-g7cb1b4663150 #0<br /> RIP: 0010:get_new_segment fs/f2fs/segment.c:2746 [inline]<br /> RIP: 0010:new_curseg+0x1f52/0x1f70 fs/f2fs/segment.c:2876<br /> Call Trace:<br /> <br /> __allocate_new_segment+0x1ce/0x940 fs/f2fs/segment.c:3210<br /> f2fs_allocate_new_section fs/f2fs/segment.c:3224 [inline]<br /> f2fs_allocate_pinning_section+0xfa/0x4e0 fs/f2fs/segment.c:3238<br /> f2fs_expand_inode_data+0x696/0xca0 fs/f2fs/file.c:1830<br /> f2fs_fallocate+0x537/0xa10 fs/f2fs/file.c:1940<br /> vfs_fallocate+0x569/0x6e0 fs/open.c:327<br /> do_vfs_ioctl+0x258c/0x2e40 fs/ioctl.c:885<br /> __do_sys_ioctl fs/ioctl.c:904 [inline]<br /> __se_sys_ioctl+0x80/0x170 fs/ioctl.c:892<br /> do_syscall_x64 arch/x86/entry/common.c:52 [inline]<br /> do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83<br /> entry_SYSCALL_64_after_hwframe+0x77/0x7f<br /> <br /> Concurrent pinfile allocation may run out of free section, result in<br /> panic in get_new_segment(), let&amp;#39;s expand pin_sem lock coverage to<br /> include f2fs_gc(), so that we can make sure to reclaim enough free<br /> space for following allocation.<br /> <br /> In addition, do below changes to enhance error path handling:<br /> - call f2fs_bug_on() only in non-pinfile allocation path in<br /> get_new_segment().<br /> - call reset_curseg_fields() to reset all fields of curseg in<br /> new_curseg()