GHSA-PHQV-2Q9M-94VV
Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-15 06:32In 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": [],
"aliases": [
"CVE-2026-68459"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-15T06:18:15Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix potential deadlock in gc_merge path of f2fs_balance_fs()\n\nWhen we mount device w/ gc_merge mount option, we may suffer below\npotential deadlock:\n\nKworker\t\t\t\t\tGC trehad\t\t\tTruncator\n- f2fs_write_cache_pages\n - f2fs_write_single_data_page\n - f2fs_do_write_data_page\n - folio_start_writeback --- set writeback flag on folio\n - f2fs_outplace_write_data\n : cached folio in internal bio cache\n - f2fs_balance_fs\n - wake_up(gc_thread)\n : wake up gc thread to run foreground GC\n - finish_wait(fggc_wq)\n : wait on the waitqueue --- wait on GC thread to finish the work\n\t\t\t\t\t\t\t\t\t- truncate_inode_pages_range\n\t\t\t\t\t\t\t\t\t - __filemap_get_folio(, FGP_LOCK) --- lock folio\n\t\t\t\t\t\t\t\t\t - truncate_inode_partial_folio\n\t\t\t\t\t\t\t\t\t - folio_wait_writeback --- wait on writeback being cleared\n\t\t\t\t\t- do_garbage_collect\n\t\t\t\t\t - move_data_page\n\t\t\t\t\t - f2fs_get_lock_data_folio\n\t\t\t\t\t - lock on folio --- blocked on folio\u0027s lock\n\nIn order to avoid such deadlock, let\u0027s call below functions to commit\ncached bios in GC_MERGE path of f2fs_balance_fs() as the same as we did\nin NOGC_MERGE path.\n- f2fs_submit_merged_write(sbi, DATA);\n- f2fs_submit_all_merged_ipu_writes(sbi);",
"id": "GHSA-phqv-2q9m-94vv",
"modified": "2026-08-15T06:32:06Z",
"published": "2026-08-15T06:32:06Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-68459"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/1436031b33fa23ab1ce7df5bc5500093413e8acf"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8071500a8124e5a6d47d901a8d5ffd91743107a1"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/89479a27fa4e1e11f378b3724944eabceb84f114"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8b4468ec023d0d1b4669dfb867588997cc03a06b"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/aa807064473abd6f2cafe419fb77ea402d3e3104"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b885c7783c19c36c7bf899492a0bffcd68afa8c7"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/eb02f218aacb36365e0ca2339cbae81fb05d31a5"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.