CVE-2025-68769: f2fs: fix return value of f2fs_recover_fsync_data()
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Fixed version: Linux Linux 01fba45deaddcce0d0b01c411435d1acf6feab7b, 0de4977a1eeafe9d77701e3c031a1bcdba389243, 4.5; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1.
Low priority for now. Upgrade to Linux Linux 01fba45deaddcce0d0b01c411435d1acf6feab7b, 0de4977a1eeafe9d77701e3c031a1bcdba389243, 4.5; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jan 13, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 1499d39b74f5957e932639a86487ccea5a0a9740, 4.7affected
- 6781eabba1bdb133eb9125c4acf6704ccbe4df02 and later · before e6ac31abd30e9fd2ef5f0819ce7f3f932be3b725affected · git
- 6781eabba1bdb133eb9125c4acf6704ccbe4df02 and later · before 0de4977a1eeafe9d77701e3c031a1bcdba389243affected · git
- 6781eabba1bdb133eb9125c4acf6704ccbe4df02 and later · before 9bc246018aaa3b46a7710428d0a2196c229f9d49affected · git
- 6781eabba1bdb133eb9125c4acf6704ccbe4df02 and later · before a4c67d96f92eefcfa5596a08f069e77b743c5865affected · git
- 6781eabba1bdb133eb9125c4acf6704ccbe4df02 and later · before 473550e715654ad7612aa490d583cb7c25fe2ff3affected · git
- 6781eabba1bdb133eb9125c4acf6704ccbe4df02 and later · before 4560db9678a2c5952b6205fbca468c6805c2ba2aaffected · git
- 6781eabba1bdb133eb9125c4acf6704ccbe4df02 and later · before 01fba45deaddcce0d0b01c411435d1acf6feab7baffected · git
- 4.4.172 and later · before 4.5affected · semver
- before 4.7not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.162-1 | 6.1.162-1 |
| Debian:13 | linux | before 6.12.69-1 | 6.12.69-1 |
| Debian:14 | linux | before 6.18.3-1 | 6.18.3-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-68767Jan 13, 2026 · hfsplus: Verify inode mode when loading from disk0Monitor
- ← EarlierCVE-2025-68768Jan 13, 2026 · inet: frags: flush pending skbs in fqdir_pre_exit()0Monitor
- Later →CVE-2025-68771Jan 13, 2026 · ocfs2: fix kernel BUG in ocfs2_find_victim_chain0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 01fba45deaddcce0d0b01c411435d1acf6feab7b | Vendor (CNA) |
| Linux Linux | 0de4977a1eeafe9d77701e3c031a1bcdba389243 | Vendor (CNA) |
| Linux Linux | 4.5 | Vendor (CNA) |
| Linux Linux | 4560db9678a2c5952b6205fbca468c6805c2ba2a | Vendor (CNA) |
| Linux Linux | 473550e715654ad7612aa490d583cb7c25fe2ff3 | Vendor (CNA) |
| Linux Linux | 9bc246018aaa3b46a7710428d0a2196c229f9d49 | Vendor (CNA) |
| Linux Linux | a4c67d96f92eefcfa5596a08f069e77b743c5865 | Vendor (CNA) |
| Linux Linux | e6ac31abd30e9fd2ef5f0819ce7f3f932be3b725 | Vendor (CNA) |
| azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 | 6.6.121.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.162-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/0de4977a1eeafe9d77701e3c031a1bcdba389243
- git.kernel.org/stable/c/4560db9678a2c5952b6205fbca468c6805c2ba2a
- git.kernel.org/stable/c/473550e715654ad7612aa490d583cb7c25fe2ff3
- git.kernel.org/stable/c/9bc246018aaa3b46a7710428d0a2196c229f9d49
- git.kernel.org/stable/c/a4c67d96f92eefcfa5596a08f069e77b743c5865
- git.kernel.org/stable/c/e6ac31abd30e9fd2ef5f0819ce7f3f932be3b725
Vendor advisories and official records. Exploit/PoC links are deliberately left out.