Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-68769f2fs: fix return value of f2fs_recover_fsync_data()

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.

Timeline

  1. ID reserved

    By Linux

  2. · 20 days later

    Published

  3. · 4 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 6781eabba1bdb133eb9125c4acf6704ccbe4df02 – < e6ac31abd30e9fd2ef5f0819ce7f3f932be3b725
    • affected 6781eabba1bdb133eb9125c4acf6704ccbe4df02 – < 0de4977a1eeafe9d77701e3c031a1bcdba389243
    • affected 6781eabba1bdb133eb9125c4acf6704ccbe4df02 – < 9bc246018aaa3b46a7710428d0a2196c229f9d49
    • affected 6781eabba1bdb133eb9125c4acf6704ccbe4df02 – < a4c67d96f92eefcfa5596a08f069e77b743c5865
    • affected 6781eabba1bdb133eb9125c4acf6704ccbe4df02 – < 473550e715654ad7612aa490d583cb7c25fe2ff3
    • affected 6781eabba1bdb133eb9125c4acf6704ccbe4df02 – < 4560db9678a2c5952b6205fbca468c6805c2ba2a
    • affected 6781eabba1bdb133eb9125c4acf6704ccbe4df02 – < 01fba45deaddcce0d0b01c411435d1acf6feab7b
    • affected 1499d39b74f5957e932639a86487ccea5a0a9740
    • affected 4.4.172 – < 4.5
  • Linux · Linux

    • affected 4.7
    • unaffected < 4.7
    • unaffected 5.10.248 – ≤ 5.10.*
    • unaffected 5.15.198 – ≤ 5.15.*
    • unaffected 6.1.160 – ≤ 6.1.*
    • unaffected 6.6.120 – ≤ 6.6.*
    • unaffected 6.12.64 – ≤ 6.12.*
    • unaffected 6.18.3 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-68769 badge
[![CVE-2025-68769](https://cveledger.app/badge/CVE-2025-68769.svg)](https://cveledger.app/cve/CVE-2025-68769)

Record last updated .