System hang via uncommitted cached writeback bios
Published Aug 15, 2026 · Updated Aug 15, 2026
Deadlock in the Linux kernel F2FS component allows local users to hang the system through concurrent writeback and truncation. The f2fs_balance_fs() GC_MERGE path waits for foreground garbage collection without first submitting cached data and in-place-update bios, while the garbage collector and truncator contend for the same folio and its writeback completion. The path is reachable only on an F2FS filesystem mounted with gc_merge, and the resulting circular wait blocks filesystem work and can cause a system-wide service interrupt.
Summary
What happened
Deadlock in the Linux kernel F2FS component allows local users to hang the system through concurrent writeback and truncation. The f2fs_balance_fs() GC_MERGE path waits for foreground garbage collection without first submitting cached data and in-place-update bios, while the garbage collector and truncator contend for the same folio and its writeback completion. The path is reachable only on an F2FS filesystem mounted with gc_merge, and the resulting circular wait blocks filesystem work and can cause a system-wide service interrupt.
The record
- CVE
- CVE-2026-68459
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-833, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 15, 2026CVE publishedPublication date reported by the CVE source.
- Aug 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=351df4b201157351c7d26bf12c3eeb9dbce98854 <1436031b33fa23ab1ce7df5bc5500093413e8acf
- Affected versionversion=351df4b201157351c7d26bf12c3eeb9dbce98854 <8071500a8124e5a6d47d901a8d5ffd91743107a1
- Affected versionversion=351df4b201157351c7d26bf12c3eeb9dbce98854 <89479a27fa4e1e11f378b3724944eabceb84f114
- Affected versionversion=351df4b201157351c7d26bf12c3eeb9dbce98854 <8b4468ec023d0d1b4669dfb867588997cc03a06b
- Affected versionversion=351df4b201157351c7d26bf12c3eeb9dbce98854 <aa807064473abd6f2cafe419fb77ea402d3e3104
- Affected versionversion=351df4b201157351c7d26bf12c3eeb9dbce98854 <b885c7783c19c36c7bf899492a0bffcd68afa8c7
- Affected versionversion=351df4b201157351c7d26bf12c3eeb9dbce98854 <eb02f218aacb36365e0ca2339cbae81fb05d31a5
- Affected versionversion=3.8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo