CVE-2025-68772 json
f2fs: fix to avoid updating compression context during writeback
published 2026-01-13 9 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-2316
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 10%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix to avoid updating compression context during writeback
Bai, Shuangpeng <sjb7183@psu.edu> reported a bug as below:
Oops: divide error: 0000 [#1] SMP KASAN PTI CPU: 0 UID: 0 PID: 11441 Comm: syz.0.46 Not tainted 6.17.0 #1 PREEMPT(full) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 RIP: 0010:f2fs_all_cluster_page_ready+0x106/0x550 fs/f2fs/compress.c:857 Call Trace: <TASK> f2fs_write_cache_pages fs/f2fs/data.c:3078 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3290 [inline] f2fs_write_data_pages+0x1c19/0x3600 fs/f2fs/data.c:3317 do_writepages+0x38e/0x640 mm/page-writeback.c:2634 filemap_fdatawrite_wbc mm/filemap.c:386 [inline] __filemap_fdatawrite_range mm/filemap.c:419 [inline] file_write_and_wait_range+0x2ba/0x3e0 mm/filemap.c:794 f2fs_do_sync_file+0x6e6/0x1b00 fs/f2fs/file.c:294 generic_write_sync include/linux/fs.h:3043 [inline] f2fs_file_write_iter+0x76e/0x2700 fs/f2fs/file.c:5259 new_sync_write fs/read_write.c:593 [inline] vfs_write+0x7e9/0xe00 fs/read_write.c:686 ksys_write+0x19d/0x2d0 fs/read_write.c:738 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xf7/0x470 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f
The bug was triggered w/ below race condition:
fsync setattr ioctl - f2fs_do_sync_file - file_write_and_wait_range - f2fs_write_cache_pages : inode is non-compressed : cc.cluster_size = F2FS_I(inode)->i_cluster_size = 0 - tag_pages_for_writeback - f2fs_setattr - truncate_setsize - f2fs_truncate - f2fs_fileattr_set - f2fs_setflags_common - set_compress_context : F2FS_I(inode)->i_cluster_size = 4 : set_inode_flag(inode, FI_COMPRESSED_FILE) - f2fs_compressed_file : return true - f2fs_all_cluster_page_ready : "pgidx % cc->cluster_size" trigger dividing 0 issue
Let's change as below to fix this issue: - introduce a new atomic type variable .writeback in structure f2fs_inode_info to track the number of threads which calling f2fs_write_cache_pages(). - use .i_sem lock to protect .writeback update. - check .writeback before update compression context in f2fs_setflags_common() to avoid race w/ ->writepages.
Patch / fix
- Linux Linux 6.1.160, 6.6.120, 6.12.64, 6.18.3, 6.19
- linux Debian 12 6.1.162-1
- linux Debian 13 6.12.69-1
- linux Debian 14 6.18.3-1
debian advisories DEBIAN-CVE-2025-68772
- linux Ubuntu 24.04 LTS 6.8.0-110.110
- linux Ubuntu 25.10 6.17.0-22.22
- linux-aws Ubuntu 24.04 LTS 6.8.0-1052.55
- linux-aws Ubuntu 25.10 6.17.0-1012.12
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1054.57
- linux-gcp Ubuntu 25.10 6.17.0-1012.12
- linux-gke Ubuntu 24.04 LTS 6.8.0-1050.56
- linux-ibm Ubuntu 24.04 LTS 6.8.0-1051.51
ubuntu advisories UBUNTU-CVE-2025-68772
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/ad26bfbc085c939b5dca77ff8c14798c06d151c4 commit
- git.kernel.org/stable/c/bcd0086ee5a2e88c1224ff2ec1e4a43c83efe5a0 commit
- git.kernel.org/stable/c/0bf1a02494c7eb5bd43445de4c83c8592e02c4bf commit
- git.kernel.org/stable/c/0df713a9c082a474c8b0bcf670edc8e98461d5a0 commit
- git.kernel.org/stable/c/10b591e7fb7cdc8c1e53e9c000dc0ef7069aaa76 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-68772 updated
kernel: f2fs: fix to avoid updating compression context during writeback
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.20% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/ad26bfbc085c939b5dca77ff8c14798c06d151c4
- git.kernel.org /stable/c/bcd0086ee5a2e88c1224ff2ec1e4a43c83efe5a0
- git.kernel.org /stable/c/0bf1a02494c7eb5bd43445de4c83c8592e02c4bf
- git.kernel.org /stable/c/0df713a9c082a474c8b0bcf670edc8e98461d5a0
- git.kernel.org /stable/c/10b591e7fb7cdc8c1e53e9c000dc0ef7069aaa76
Sources
- CVE List CVE-2025-68772
- NVD CVE-2025-68772
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.