CVE-2025-68796
Last modified
CVE-2025-68796 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid updating zero-sized extent in extent cache As syzbot reported: F2FS-fs (loop0): __update_extent_tree_range: extent len is zero, type: 0, extent [0, 0, 0], age [0, 0] ------------[ cut here ]------------ kernel BUG at fs/f2fs/extent_cache.c:678! Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI CPU: 0 UID: 0 PID: 5336 Comm: syz.0.0 Not tainted syzkaller #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 RIP: 0010:__update_extent_tree_range+0x13bc/0x1500 fs/f2fs/extent_cache.c:678 Call Trace: <TASK> f2fs_update_read_extent_cache_range+0x192/0x3e0 fs/f2fs/extent_cache.c:1085 f2fs_do_zero_range fs/f2fs/file.c:1657 [inline] f2fs_zero_range+0x10c1/0x1580 fs/f2fs/file.c:1737 f2fs_fallocate+0x583/0x990 fs/f2fs/file.c:2030 vfs_fallocate+0x669/0x7e0 fs/open.c:342 ioctl_preallocate fs/ioctl.c:289 [inline] file_ioctl+0x611/0x780 fs/ioctl.c:-1 do_vfs_ioctl+0xb33/0x1430 fs/ioctl.c:576 __do_sys_ioctl fs/ioctl.c:595 [inline] __se_sys_ioctl+0x82/0x170 fs/ioctl.c:583 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f07bc58eec9 In error path of f2fs_zero_range(), it may add a zero-sized extent into extent cache, it should be avoided.. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid updating zero-sized extent in extent cache As syzbot reported: F2FS-fs (loop0): __update_extent_tree_range: extent len is zero, type: 0, extent [0, 0, 0], age [0, 0] ------------[ cut here ]------------ kernel BUG at fs/f2fs/extent_cache.c:678! Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI CPU: 0 UID: 0 PID: 5336 Comm: syz.0.0 Not tainted syzkaller #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 RIP: 0010:__update_extent_tree_range+0x13bc/0x1500 fs/f2fs/extent_cache.c:678 Call Trace: <TASK> f2fs_update_read_extent_cache_range+0x192/0x3e0 fs/f2fs/extent_cache.c:1085 f2fs_do_zero_range fs/f2fs/file.c:1657 [inline] f2fs_zero_range+0x10c1/0x1580 fs/f2fs/file.c:1737 f2fs_fallocate+0x583/0x990 fs/f2fs/file.c:2030 vfs_fallocate+0x669/0x7e0 fs/open.c:342 ioctl_preallocate fs/ioctl.c:289 [inline] file_ioctl+0x611/0x780 fs/ioctl.c:-1 do_vfs_ioctl+0xb33/0x1430 fs/ioctl.c:576 __do_sys_ioctl fs/ioctl.c:595 [inline] __se_sys_ioctl+0x82/0x170 fs/ioctl.c:583 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f07bc58eec9 In error path of f2fs_zero_range(), it may add a zero-sized extent into extent cache, it should be avoided.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 6e9619499f53b22ead972e476c0e8341c997d929, < 9c07bd262c13ca922adad6e7613d48505f97f548; >= 6e9619499f53b22ead972e476c0e8341c997d929, < 72c58a82e6fb7b327e8701f5786c70c3edc56188; >= 6e9619499f53b22ead972e476c0e8341c997d929, < e50b81c50fcbe63f50405bb40f262162ff32af88; >= 6e9619499f53b22ead972e476c0e8341c997d929, < efe3371001f50a2d6f746b50bdc6f9f26b2089ec; >= 6e9619499f53b22ead972e476c0e8341c997d929, < 4f244c64efe628d277b916f47071adf480eb8646; >= 6e9619499f53b22ead972e476c0e8341c997d929, < bac23833220a1f8fe8dfab7e16efa20ff64d7589; >= 6e9619499f53b22ead972e476c0e8341c997d929, < 7c37c79510329cd951a4dedf3f7bf7e2b18dccec |
| Linux | Linux | 4.7 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2025-68796?
How severe is CVE-2025-68796?
How do I fix CVE-2025-68796?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-68790In the Linux kernel, the following vulnerability has been re…
- CVE-2025-68791In the Linux kernel, the following vulnerability has been re…
- CVE-2025-68792In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-68793In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-68794In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2025-68795In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-68797In the Linux kernel, the following vulnerability has been re…
- CVE-2025-68798In the Linux kernel, the following vulnerability has been re…
- CVE-2025-68799In the Linux kernel, the following vulnerability has been re…8.1
- CVE-2025-6880A vulnerability classified as critical has been found in Sou…8.8
- CVE-2025-68800In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-68801In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2025-68796?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
