I/O hang via inconsistent current-segment state
Published Nov 20, 2026 · Updated Nov 20, 2026
Linux F2FS has a race that allows local users to crash a writeback worker and hang I/O during atomic writes and shutdown. In fs/f2fs/segment.c, change_curseg() leaves the current segment inconsistent after a summary-read failure, causing subsequent block allocation to trigger a kernel BUG. The documented trigger requires concurrent atomic-write commit, filesystem shutdown, and writeback; the worker dies holding locks, blocking other I/O threads.
Summary
What happened
Linux F2FS has a race that allows local users to crash a writeback worker and hang I/O during atomic writes and shutdown. In fs/f2fs/segment.c, change_curseg() leaves the current segment inconsistent after a summary-read failure, causing subsequent block allocation to trigger a kernel BUG. The documented trigger requires concurrent atomic-write commit, filesystem shutdown, and writeback; the worker dies holding locks, blocking other I/O threads.
The record
- CVE
- CVE-2026-99570
- Published
- Nov 20, 2026
- Updated
- Nov 20, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 20, 2026CVE publishedPublication date reported by the CVE source.
- Nov 20, 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=5.10
- Affected versionversion=5.4.75 <5.5
- Affected versionversion=5.9.5 <5.10
- Affected versionversion=6b67737f2dde60fbad8ddac37c8653e3c3bf0855
- Affected versionversion=86f33603f8c51537265ff7ac0320638fd2cbdb1b <1c9ccd9eadf1707a2149c3237b85f1f82ce92702
- Affected versionversion=86f33603f8c51537265ff7ac0320638fd2cbdb1b <c2de116785396df236e311e7643913212fe9fe50
- Affected versionversion=86f33603f8c51537265ff7ac0320638fd2cbdb1b <c8e6c10f95643dd88e73e7daa8ceb1041631920c
- Affected versionversion=86f33603f8c51537265ff7ac0320638fd2cbdb1b <e74476ad8162c1facc74b74ce2d1372492df872e
- Affected versionversion=df5b07f2172a159a4d9f0c280e6ecddba992ba35
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us