---
cve: "CVE-2025-68769"
severity: "LOW"
cvss: 3.1
epss: "18%"
vendor: "Linux"
kev: false
exploited: false
published: "2026-01-13 16:15:56"
tags: [cve, security, low]
source: tsecurity.de CVE-Dossier
exported: "2026-09-18T05:11:48+02:00"
---

# CVE-2025-68769

> 3.1 LOW

## Beschreibung

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:
 
 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.

## Patch verfügbar (OSV)

- Kernel ≥ 5.10.248
- Kernel ≥ 5.15.198
- Kernel ≥ 6.1.160
- Kernel ≥ 6.6.120
- Kernel ≥ 6.12.64
- Kernel ≥ 6.18.3

## Referenzen

- <https://git.kernel.org/stable/c/e6ac31abd30e9fd2ef5f0819ce7f3f932be3b725>
- <https://git.kernel.org/stable/c/0de4977a1eeafe9d77701e3c031a1bcdba389243>
- <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>

---
_Exportiert aus dem [tsecurity.de CVE-Dossier](https://tsecurity.de/cve?cve=CVE-2025-68769) · Datenquellen: EUVD (ENISA), NVD, OSV, CISA KEV, FIRST EPSS, Exploit-DB, BSI BITS_