CVE-2026-68459

f2fs: fix potential deadlock in gc_merge path of f2fs_balance_fs()

N/A
Published: August 15, 2026 at 05:51 AM UTC
Updated: August 17, 2026 at 06:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix potential deadlock in gc_merge path of f2fs_balance_fs() When we mount device w/ gc_merge mount option, we may suffer below potential deadlock: Kworker GC trehad Truncator - f2fs_write_cache_pages - f2fs_write_single_data_page - f2fs_do_write_data_page - folio_start_writeback --- set writeback flag on folio - f2fs_outplace_write_data : cached folio in internal bio cache - f2fs_balance_fs - wake_up(gc_thread) : wake up gc thread to run foreground GC - finish_wait(fggc_wq) : wait on the waitqueue --- wait on GC thread to finish the work - truncate_inode_pages_range - __filemap_get_folio(, FGP_LOCK) --- lock folio - truncate_inode_partial_folio - folio_wait_writeback --- wait on writeback being cleared - do_garbage_collect - move_data_page - f2fs_get_lock_data_folio - lock on folio --- blocked on folio's lock In order to avoid such deadlock, let's call below functions to commit cached bios in GC_MERGE path of f2fs_balance_fs() as the same as we did in NOGC_MERGE path. - f2fs_submit_merged_write(sbi, DATA); - f2fs_submit_all_merged_ipu_writes(sbi);

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.8 ≤ v < 5.15.2123.8 ≤ v < 6.1.1783.8 ≤ v < 6.12.963.8 ≤ v < 6.18.393.8 ≤ v < 6.6.1453.8 ≤ v < 7.1.53.8 ≤ v < 7.23.8351df4b201157351c7d26bf12c3eeb9dbce98854
Vendor states this is fixed in 1436031b33fa23ab1ce7df5bc5500093413e8acf (fixed)
Vendor states this is fixed in 8071500a8124e5a6d47d901a8d5ffd91743107a1 (fixed)
Vendor states this is fixed in 89479a27fa4e1e11f378b3724944eabceb84f114 (fixed)
Vendor states this is fixed in 8b4468ec023d0d1b4669dfb867588997cc03a06b (fixed)
Vendor states this is fixed in aa807064473abd6f2cafe419fb77ea402d3e3104 (fixed)
Vendor states this is fixed in b885c7783c19c36c7bf899492a0bffcd68afa8c7 (fixed)
Vendor states this is fixed in eb02f218aacb36365e0ca2339cbae81fb05d31a5 (fixed)
Vendor states this is fixed in 3.8 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.96 (unaffected)
Vendor states this is fixed in 6.18.39 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card