CVE-2026-68459f2fs: fix potential deadlock in gc_merge path of f2fs_balance_fs()
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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);
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Aug 17, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 351df4b201157351c7d26bf12c3eeb9dbce98854 before 8071500a8124e5a6d47d901a8d5ffd91743107a1; from 351df4b201157351c7d26bf12c3eeb9dbce98854 before eb02f218aacb36365e0ca2339cbae81fb05d31a5; from 351df4b201157351c7d26bf12c3eeb9dbce98854 before 1436031b33fa23ab1ce7df5bc5500093413e8acf; from 351df4b201157351c7d26bf12c3eeb9dbce98854 before b885c7783c19c36c7bf899492a0bffcd68afa8c7; from 351df4b201157351c7d26bf12c3eeb9dbce98854 before 89479a27fa4e1e11f378b3724944eabceb84f114; from 351df4b201157351c7d26bf12c3eeb9dbce98854 before aa807064473abd6f2cafe419fb77ea402d3e3104; 351df4b201157351c7d26bf12c3eeb9dbce98854 builds before 8b4468ec023d0d1b4669dfb867588997cc03a06b | CNA record |
References
- https://git.kernel.org/stable/c/8071500a8124e5a6d47d901a8d5ffd91743107a1
- https://git.kernel.org/stable/c/eb02f218aacb36365e0ca2339cbae81fb05d31a5
- https://git.kernel.org/stable/c/1436031b33fa23ab1ce7df5bc5500093413e8acf
- https://git.kernel.org/stable/c/b885c7783c19c36c7bf899492a0bffcd68afa8c7
- https://git.kernel.org/stable/c/89479a27fa4e1e11f378b3724944eabceb84f114
- https://git.kernel.org/stable/c/aa807064473abd6f2cafe419fb77ea402d3e3104
- https://git.kernel.org/stable/c/8b4468ec023d0d1b4669dfb867588997cc03a06b
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.