CVE-2025-68769

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> f2fs: fix return value of f2fs_recover_fsync_data()<br /> <br /> With below scripts, it will trigger panic in f2fs:<br /> <br /> mkfs.f2fs -f /dev/vdd<br /> mount /dev/vdd /mnt/f2fs<br /> touch /mnt/f2fs/foo<br /> sync<br /> echo 111 &gt;&gt; /mnt/f2fs/foo<br /> f2fs_io fsync /mnt/f2fs/foo<br /> f2fs_io shutdown 2 /mnt/f2fs<br /> umount /mnt/f2fs<br /> mount -o ro,norecovery /dev/vdd /mnt/f2fs<br /> or<br /> mount -o ro,disable_roll_forward /dev/vdd /mnt/f2fs<br /> <br /> F2FS-fs (vdd): f2fs_recover_fsync_data: recovery fsync data, check_only: 0<br /> F2FS-fs (vdd): Mounted with checkpoint version = 7f5c361f<br /> F2FS-fs (vdd): Stopped filesystem due to reason: 0<br /> F2FS-fs (vdd): f2fs_recover_fsync_data: recovery fsync data, check_only: 1<br /> Filesystem f2fs get_tree() didn&amp;#39;t set fc-&gt;root, returned 1<br /> ------------[ cut here ]------------<br /> kernel BUG at fs/super.c:1761!<br /> Oops: invalid opcode: 0000 [#1] SMP PTI<br /> CPU: 3 UID: 0 PID: 722 Comm: mount Not tainted 6.18.0-rc2+ #721 PREEMPT(voluntary)<br /> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014<br /> RIP: 0010:vfs_get_tree.cold+0x18/0x1a<br /> Call Trace:<br /> <br /> fc_mount+0x13/0xa0<br /> path_mount+0x34e/0xc50<br /> __x64_sys_mount+0x121/0x150<br /> do_syscall_64+0x84/0x800<br /> entry_SYSCALL_64_after_hwframe+0x76/0x7e<br /> RIP: 0033:0x7fa6cc126cfe<br /> <br /> The root cause is we missed to handle error number returned from<br /> f2fs_recover_fsync_data() when mounting image w/ ro,norecovery or<br /> ro,disable_roll_forward mount option, result in returning a positive<br /> error number to vfs_get_tree(), fix it.