f2fs: fix to avoid updating zero-sized extent in extent cache
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.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for help- Published
- Jan 13, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 9th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Affected systems
—
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
- 4.7affected
- 6e9619499f53b22ead972e476c0e8341c997d929 and later · before 9c07bd262c13ca922adad6e7613d48505f97f548affected · git
- 6e9619499f53b22ead972e476c0e8341c997d929 and later · before 72c58a82e6fb7b327e8701f5786c70c3edc56188affected · git
- 6e9619499f53b22ead972e476c0e8341c997d929 and later · before e50b81c50fcbe63f50405bb40f262162ff32af88affected · git
- 6e9619499f53b22ead972e476c0e8341c997d929 and later · before efe3371001f50a2d6f746b50bdc6f9f26b2089ecaffected · git
- 6e9619499f53b22ead972e476c0e8341c997d929 and later · before 4f244c64efe628d277b916f47071adf480eb8646affected · git
- 6e9619499f53b22ead972e476c0e8341c997d929 and later · before bac23833220a1f8fe8dfab7e16efa20ff64d7589affected · git
- 6e9619499f53b22ead972e476c0e8341c997d929 and later · before 7c37c79510329cd951a4dedf3f7bf7e2b18dccecaffected · git
- before 4.7not affected · semver
- 5.10.248 and later · up to and including 5.10.*not 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
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
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 | 4f244c64efe628d277b916f47071adf480eb8646 | Vendor (CNA) |
| Linux Linux | 72c58a82e6fb7b327e8701f5786c70c3edc56188 | Vendor (CNA) |
| Linux Linux | 7c37c79510329cd951a4dedf3f7bf7e2b18dccec | Vendor (CNA) |
| Linux Linux | 9c07bd262c13ca922adad6e7613d48505f97f548 | Vendor (CNA) |
| Linux Linux | bac23833220a1f8fe8dfab7e16efa20ff64d7589 | Vendor (CNA) |
| Linux Linux | e50b81c50fcbe63f50405bb40f262162ff32af88 | Vendor (CNA) |
| Linux Linux | efe3371001f50a2d6f746b50bdc6f9f26b2089ec | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/4f244c64efe628d277b916f47071adf480eb8646
- git.kernel.org/stable/c/72c58a82e6fb7b327e8701f5786c70c3edc56188
- git.kernel.org/stable/c/7c37c79510329cd951a4dedf3f7bf7e2b18dccec
- git.kernel.org/stable/c/9c07bd262c13ca922adad6e7613d48505f97f548
- git.kernel.org/stable/c/bac23833220a1f8fe8dfab7e16efa20ff64d7589
- git.kernel.org/stable/c/e50b81c50fcbe63f50405bb40f262162ff32af88
- git.kernel.org/stable/c/efe3371001f50a2d6f746b50bdc6f9f26b2089ec
Vendor advisories and official records. Exploit/PoC links are deliberately left out.