Skip to main content
Menu
CVEs

Linux kernel denial of service in F2FS file system

CVE-2026-99570Published November 20, 2026, updated

Exploited
No known exploitation
Fix
Fixed in 5.5, 5.10
Who is exposed
Not reported

Summary

The f2fs file system in the Linux kernel mishandles a race between an atomic write commit and a filesystem shutdown, which can trigger a kernel BUG and crash the system. The current segment is not invalidated when its change fails, so a later write can hit a failed allocation check.

Written by a model

Original description

In the Linux kernel, the following vulnerability has been resolved:

f2fs: fix to invalidate curseg if change_curseg() fails

Our consistency stress test (fsstress + fio + atomic write workers + "f2fs_io shutdown 1") triggers below kernel BUG:

F2FS-fs (vdd): Stopped filesystem due to reason: 0 ------------[ cut here ]------------ kernel BUG at fs/f2fs/segment.c:3989! Oops: invalid opcode: 0000 [#1] SMP KASAN PTI Workqueue: writeback wb_workfn (flush-253:48) RIP: 0010:f2fs_allocate_data_block+0x257a/0x38e0 Call Trace: <TASK> do_write_block+0x155/0xc10 f2fs_outplace_write_data+0x192/0x340 f2fs_do_write_data_page+0xc57/0x1880 f2fs_write_single_data_page+0xda9/0x15a0 f2fs_write_cache_pages+0x973/0x1f20 __f2fs_write_data_pages+0x6c4/0x1890 do_writepages+0x21e/0x560 __writeback_single_inode+0x119/0x11b0 writeback_sb_inodes+0x67d/0x17a0 wb_writeback+0x207/0x820 wb_workfn+0x128/0xc30 process_one_work+0x925/0x1600 worker_thread+0x60a/0xff0 kthread+0x35f/0x460 ret_from_fork+0x474/0x7e0 ret_from_fork_asm+0x1a/0x30 </TASK>

The BUG is f2fs_bug_on(sbi, curseg->next_blkoff >= BLKS_PER_SEG(sbi)) in f2fs_allocate_data_block(), next_blkoff was 512.

The root cause is a race in between atomic write commit and shutdown as below:

Thread A (commit atomic write) Thread B (shutdown) Thread C (writeback)

  • f2fs_ioc_commit_atomic_write
  • f2fs_commit_atomic_write
  • __f2fs_commit_atomic_write
  • __replace_atomic_write_block
  • f2fs_replace_block
  • __f2fs_replace_block
  • f2fs_ioc_shutdown
  • f2fs_do_shutdown : F2FS_GOING_DOWN_METASYNC
  • f2fs_sync_fs
  • f2fs_write_single_data_page : pass f2fs_cp_error() check
  • f2fs_stop_checkpoint : set CP_ERROR_FLAG
  • change_curseg
  • reset_curseg : curseg->segno = new_segno : curseg->alloc_type = SSR : curseg->next_blkoff = __next_free_blkoff() which is BLKS_PER_SEG if there is no free slot in new_segno
  • f2fs_get_sum_cache : return -EIO due to f2fs_cp_error() : return error w/o restoring curseg : goto out_unlock, skip restoring old segno, blkoff and alloc_type
  • f2fs_do_write_data_page
  • f2fs_outplace_write_data
  • do_write_block
  • f2fs_allocate_data_block : curseg->segno is valid : f2fs_bug_on(next_blkoff >= BLKS_PER_SEG)

Since commit 86f33603f8c5 ("f2fs: handle errors of f2fs_get_meta_page_nofail"), change_curseg() can fail after the curseg has already been switched to the new segment, then the curseg is left in an inconsistent state: it points to a segment which may have no free slot, its summary block is zeroed, and the caller can not restore it. Subsequent block allocation on the curseg will trigger the BUG. Moreover, the writeback thread dies with curseg_lock, curseg_mutex and sentry_lock held, so the commit, shutdown and other I/O threads hang in D state.

Since change_curseg() only fails once CP_ERROR_FLAG is set, no checkpoint will be committed afterward, let's invalidate the curseg via reset_curseg_fields() on failure, as new_curseg() does for -ENOSPC, then f2fs_allocate_data_block() will fail with -ENOSPC on the curseg instead of triggering BUG, and do_write_block() can handle the error since CP_ERROR_FLA ---truncated---

What to do

Upgrade to a fixed version: 5.5, 5.10.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-99570 (f2fs: fix to invalidate curseg if change_curseg() fails), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-99570 (entry last updated 2026-11-20):
Affected:
- Linux Linux: from 5.4.75, fixed in 5.5; from 5.9.5, fixed in 5.10
- Linux Linux: versions 5.10
Fixed versions: 5.5, 5.10.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99570 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99570 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/1c9ccd9eadf1707a2149c3237b85f1f82ce92702
- https://git.kernel.org/stable/c/c8e6c10f95643dd88e73e7daa8ceb1041631920c
- https://git.kernel.org/stable/c/c2de116785396df236e311e7643913212fe9fe50
- https://git.kernel.org/stable/c/e74476ad8162c1facc74b74ce2d1372492df872e
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-99570
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99570"}.

Affected versions

cve.now Index

20Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach20/20Affects Linux kernel (software on nearly every server, desktop or phone)
  • Severity?/10Unknown. No CVSS score or vendor rating
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 42 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 6

Questions about CVE-2026-99570

Is CVE-2026-99570 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-99570?

Linux: from 5.4.75 before 5.5; from 5.9.5 before 5.10. Linux: version 5.10.

Source: cve.now feed data

How do I fix CVE-2026-99570?

Upgrade to a fixed version: 5.5, 5.10.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.