linux-cve-announce - CVE-2025-68769: f2fs: fix return value of f2fs_recover_fsync

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2026011357-CVE-2025-68769-e471@gregkh>
Date: Tue, 13 Jan 2026 16:28:55 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-68769: f2fs: fix return value of f2fs_recover_fsync_data()

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

f2fs: fix return value of f2fs_recover_fsync_data()

With below scripts, it will trigger panic in f2fs:

mkfs.f2fs -f /dev/vdd
mount /dev/vdd /mnt/f2fs
touch /mnt/f2fs/foo
sync
echo 111 >> /mnt/f2fs/foo
f2fs_io fsync /mnt/f2fs/foo
f2fs_io shutdown 2 /mnt/f2fs
umount /mnt/f2fs
mount -o ro,norecovery /dev/vdd /mnt/f2fs
or
mount -o ro,disable_roll_forward /dev/vdd /mnt/f2fs

F2FS-fs (vdd): f2fs_recover_fsync_data: recovery fsync data, check_only: 0
F2FS-fs (vdd): Mounted with checkpoint version = 7f5c361f
F2FS-fs (vdd): Stopped filesystem due to reason: 0
F2FS-fs (vdd): f2fs_recover_fsync_data: recovery fsync data, check_only: 1
Filesystem f2fs get_tree() didn't set fc->root, returned 1
------------[ cut here ]------------
kernel BUG at fs/super.c:1761!
Oops: invalid opcode: 0000 [#1] SMP PTI
CPU: 3 UID: 0 PID: 722 Comm: mount Not tainted 6.18.0-rc2+ #721 PREEMPT(voluntary)
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
RIP: 0010:vfs_get_tree.cold+0x18/0x1a
Call Trace:
 <TASK>
 fc_mount+0x13/0xa0
 path_mount+0x34e/0xc50
 __x64_sys_mount+0x121/0x150
 do_syscall_64+0x84/0x800
 entry_SYSCALL_64_after_hwframe+0x76/0x7e
RIP: 0033:0x7fa6cc126cfe

The root cause is we missed to handle error number returned from
f2fs_recover_fsync_data() when mounting image w/ ro,norecovery or
ro,disable_roll_forward mount option, result in returning a positive
error number to vfs_get_tree(), fix it.

The Linux kernel CVE team has assigned CVE-2025-68769 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 4.7 with commit 6781eabba1bdb133eb9125c4acf6704ccbe4df02 and fixed in 6.1.160 with commit 9bc246018aaa3b46a7710428d0a2196c229f9d49
	Issue introduced in 4.7 with commit 6781eabba1bdb133eb9125c4acf6704ccbe4df02 and fixed in 6.6.120 with commit a4c67d96f92eefcfa5596a08f069e77b743c5865
	Issue introduced in 4.7 with commit 6781eabba1bdb133eb9125c4acf6704ccbe4df02 and fixed in 6.12.64 with commit 473550e715654ad7612aa490d583cb7c25fe2ff3
	Issue introduced in 4.7 with commit 6781eabba1bdb133eb9125c4acf6704ccbe4df02 and fixed in 6.18.3 with commit 4560db9678a2c5952b6205fbca468c6805c2ba2a
	Issue introduced in 4.7 with commit 6781eabba1bdb133eb9125c4acf6704ccbe4df02 and fixed in 6.19-rc1 with commit 01fba45deaddcce0d0b01c411435d1acf6feab7b
	Issue introduced in 4.4.172 with commit 1499d39b74f5957e932639a86487ccea5a0a9740

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2025-68769
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	fs/f2fs/super.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/9bc246018aaa3b46a7710428d0a2196c229f9d49
	https://git.kernel.org/stable/c/a4c67d96f92eefcfa5596a08f069e77b743c5865
	https://git.kernel.org/stable/c/473550e715654ad7612aa490d583cb7c25fe2ff3
	https://git.kernel.org/stable/c/4560db9678a2c5952b6205fbca468c6805c2ba2a
	https://git.kernel.org/stable/c/01fba45deaddcce0d0b01c411435d1acf6feab7b