CVE-2025-68769
BaseFortify
Publication date: 2026-01-13
Last updated on: 2026-01-19
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is in the Linux kernel's F2FS filesystem. It occurs because the kernel missed handling an error returned from the function f2fs_recover_fsync_data() when mounting an F2FS image with the mount options ro,norecovery or ro,disable_roll_forward. This causes the function to return a positive error number to vfs_get_tree(), which leads to a kernel panic (system crash) during the mount operation.
How can this vulnerability impact me? :
This vulnerability can cause the Linux system to panic and crash when mounting an F2FS filesystem with certain options (ro,norecovery or ro,disable_roll_forward). This can lead to system instability, potential data loss, and denial of service as the filesystem becomes unusable until the system is rebooted or fixed.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by running the provided sequence of commands that trigger the panic in the f2fs filesystem. The commands are: 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 alternatively: mount -o ro,disable_roll_forward /dev/vdd /mnt/f2fs If the system panics or logs messages similar to the kernel BUG at fs/super.c:1761 or related f2fs_recover_fsync_data errors, the vulnerability is present.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves avoiding mounting f2fs filesystems with the options 'ro,norecovery' or 'ro,disable_roll_forward' until the kernel is patched. Additionally, refrain from running the sequence of commands that trigger the panic. Applying the kernel update that fixes the return value handling of f2fs_recover_fsync_data() is necessary to fully resolve the issue.