Vulnerability · Published Jan 13, 2026 · Assigned by Linux
CVE-2025-68769f2fs: fix return value of f2fs_recover_fsync_data()
Unrated
In plain English
A security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 11% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official 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.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.162-1 | DEBIAN-CVE-2025-68769 |
| Debian:13 | linux | 6.12.69-1 | DSA-6126-1 |
| Debian:13 | linux | 6.12.69-1 | DEBIAN-CVE-2025-68769 |
| Debian:14 | linux | 6.18.3-1 | DEBIAN-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux | 5.15.0-173.183 | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux | 6.8.0-110.110 | UBUNTU-CVE-2025-68769 |
| Ubuntu:25.10 | linux | 6.17.0-22.22 | UBUNTU-CVE-2025-68769 |
| Ubuntu:25.10 | linux | 6.17.0-22.22 | USN-8177-1 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1103.110 | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1052.55 | UBUNTU-CVE-2025-68769 |
| Ubuntu:25.10 | linux-aws | 6.17.0-1012.12 | UBUNTU-CVE-2025-68769 |
| Ubuntu:25.10 | linux-aws | 6.17.0-1012.12 | USN-8183-2 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-aws-6.14 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | 6.17.0-1012.12~24.04.1 | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | 6.17.0-1012.12~24.04.1 | USN-8183-2 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1052.55~22.04.1 | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1109.118 | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1054.60 | UBUNTU-CVE-2025-68769 |
| Ubuntu:25.10 | linux-azure | 6.17.0-1013.13 | UBUNTU-CVE-2025-68769 |
| Ubuntu:25.10 | linux-azure | 6.17.0-1013.13 | USN-8245-1 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-azure-6.14 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-azure-6.17 | 6.17.0-1013.13~24.04.1 | USN-8245-1 |
| Ubuntu:24.04:LTS | linux-azure-6.17 | 6.17.0-1013.13~24.04.1 | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1059.65~22.04.1 | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1109.118.1 | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-azure-fde | 6.8.0-1058.65 | UBUNTU-CVE-2025-68769 |
| Ubuntu:25.10 | linux-azure-fde | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.14 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1058.65~22.04.1 | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-azure-nvidia | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-azure-nvidia-6.14 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1103.112 | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1054.57 | UBUNTU-CVE-2025-68769 |
| Ubuntu:25.10 | linux-gcp | 6.17.0-1012.12 | USN-8183-1 |
| Ubuntu:25.10 | linux-gcp | 6.17.0-1012.12 | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-gcp-6.14 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | 6.17.0-1012.12~24.04.1 | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | 6.17.0-1012.12~24.04.1 | USN-8183-1 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1054.57~22.04.1 | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1099.105 | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1050.56 | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1086.94 | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1037.40 | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-hwe-6.14 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-hwe-6.17 | 6.17.0-22.22~24.04.1 | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-hwe-6.17 | 6.17.0-22.22~24.04.1 | USN-8183-2 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | 6.8.0-110.110~22.04.1 | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1097.100 | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1051.51 | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | 6.8.0-1051.51~22.04.1 | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1098.104 | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1095.100 | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-173.183 | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-110.110.1 | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-110.110.1~22.04.1 | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1098.99 | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1051.54 | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-nvidia-6.17 | 6.17.0-1018.18 | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1051.54~22.04.1 | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1051.54.1 | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1055.55 | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-nvidia-tegra | 6.8.0-1022.22 | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1044.44 | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-oem-6.14 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-oem-6.17 | 6.17.0-1020.20 | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-oem-6.17 | 6.17.0-1020.20 | USN-8245-1 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1100.106 | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1049.50 | UBUNTU-CVE-2025-68769 |
| Ubuntu:25.10 | linux-oracle | 6.17.0-1011.11 | USN-8183-2 |
| Ubuntu:25.10 | linux-oracle | 6.17.0-1011.11 | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-oracle-6.14 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-oracle-6.17 | 6.17.0-1011.11~24.04.1 | USN-8183-2 |
| Ubuntu:24.04:LTS | linux-oracle-6.17 | 6.17.0-1011.11~24.04.1 | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1049.50~22.04.1 | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1097.100 | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1052.56 | UBUNTU-CVE-2025-68769 |
| Ubuntu:25.10 | linux-raspi | 6.17.0-1013.13 | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:25.10 | linux-realtime | 6.17.0-1010.11 | USN-8177-1 |
| Ubuntu:25.10 | linux-realtime | 6.17.0-1010.11 | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:25.10 | linux-riscv | 6.17.0-22.22.1 | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-riscv-6.17 | 6.17.0-22.22.1~24.04.1 | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-riscv-6.8 | 6.8.0-110.110~22.04.1 | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2025-68769 |
| Ubuntu:24.04:LTS | linux-xilinx | 6.8.0-1028.29 | UBUNTU-CVE-2025-68769 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1067.71 | UBUNTU-CVE-2025-68769 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 6781eabba1bdb133eb9125c4acf6704ccbe4df02 – before e6ac31abd30e9fd2ef5f0819ce7f3f932be3b7256781eabba1bdb133eb9125c4acf6704ccbe4df02 – before 0de4977a1eeafe9d77701e3c031a1bcdba3892436781eabba1bdb133eb9125c4acf6704ccbe4df02 – before 9bc246018aaa3b46a7710428d0a2196c229f9d496781eabba1bdb133eb9125c4acf6704ccbe4df02 – before a4c67d96f92eefcfa5596a08f069e77b743c58656781eabba1bdb133eb9125c4acf6704ccbe4df02 – before 473550e715654ad7612aa490d583cb7c25fe2ff36781eabba1bdb133eb9125c4acf6704ccbe4df02 – before 4560db9678a2c5952b6205fbca468c6805c2ba2a6781eabba1bdb133eb9125c4acf6704ccbe4df02 – before 01fba45deaddcce0d0b01c411435d1acf6feab7b1499d39b74f5957e932639a86487ccea5a0a9740 |
| Linux | Linux | 4.7 |
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