CVE-2026-68459f2fs: fix potential deadlock in gc_merge path of f2fs_balance_fs()
- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 88% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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);
Timeline
ID reserved
By Linux
- 16 days later
· 16 days later
Published
- 2 days later
· 2 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.21% · top 88% of all CVEs (14 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 351df4b201157351c7d26bf12c3eeb9dbce98854 – < 8071500a8124e5a6d47d901a8d5ffd91743107a1
- affected 351df4b201157351c7d26bf12c3eeb9dbce98854 – < eb02f218aacb36365e0ca2339cbae81fb05d31a5
- affected 351df4b201157351c7d26bf12c3eeb9dbce98854 – < 1436031b33fa23ab1ce7df5bc5500093413e8acf
- affected 351df4b201157351c7d26bf12c3eeb9dbce98854 – < b885c7783c19c36c7bf899492a0bffcd68afa8c7
- affected 351df4b201157351c7d26bf12c3eeb9dbce98854 – < 89479a27fa4e1e11f378b3724944eabceb84f114
- affected 351df4b201157351c7d26bf12c3eeb9dbce98854 – < aa807064473abd6f2cafe419fb77ea402d3e3104
- affected 351df4b201157351c7d26bf12c3eeb9dbce98854 – < 8b4468ec023d0d1b4669dfb867588997cc03a06b
- affected 3.8
- unaffected < 3.8
- unaffected 5.15.212 – ≤ 5.15.*
- unaffected 6.1.178 – ≤ 6.1.*
- unaffected 6.6.145 – ≤ 6.6.*
- unaffected 6.12.96 – ≤ 6.12.*
- unaffected 6.18.39 – ≤ 6.18.*
- unaffected 7.1.5 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References7
- https://git.kernel.org/stable/c/8071500a8124e5a6d47d901a8d5ffd91743107a1 (opens in a new tab)
- https://git.kernel.org/stable/c/eb02f218aacb36365e0ca2339cbae81fb05d31a5 (opens in a new tab)
- https://git.kernel.org/stable/c/1436031b33fa23ab1ce7df5bc5500093413e8acf (opens in a new tab)
- https://git.kernel.org/stable/c/b885c7783c19c36c7bf899492a0bffcd68afa8c7 (opens in a new tab)
- https://git.kernel.org/stable/c/89479a27fa4e1e11f378b3724944eabceb84f114 (opens in a new tab)
- https://git.kernel.org/stable/c/aa807064473abd6f2cafe419fb77ea402d3e3104 (opens in a new tab)
- https://git.kernel.org/stable/c/8b4468ec023d0d1b4669dfb867588997cc03a06b (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-59081 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-68459)Record last updated .