f2fs: fix potential deadlock in gc_merge path of f2fs_balance_fs()
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);
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.15.212, 6.1.178, 6.12.96, 6.18.39, 6.6.145, 7.1.5
- CVEs
- CVE-2026-68459
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 06:31 UTC · Revision 1
Source evidence
f2fs: fix potential deadlock in gc_merge path of f2fs_balance_fs()
core-osv · Original sourcePublished 15 Aug 2026, 05:51 UTC
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);
osv:CVE-2026-68459
Kernel
Fixed versions: 5.15.212, 6.1.178, 6.6.145, 6.12.96, 6.18.39, 7.1.5
Complete source record
{
"id": "0b8e84350993a7d01dc1ff0ad20a9e7c40713dda59c08c93cc3439bdd44bd525",
"url": "https://osv.dev/vulnerability/CVE-2026-68459",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "f2fs: fix potential deadlock in gc_merge path of f2fs_balance_fs()",
"summary": "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);",
"evidence": "osv:CVE-2026-68459",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.15.212",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.178",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.145",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.96",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.39",
"evidence": "/affected/1/ranges"
},
{
"value": "7.1.5",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-68459",
"aliases": [
"CVE-2026-68459"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "351df4b201157351c7d26bf12c3eeb9dbce98854"
},
{
"fixed": "8071500a8124e5a6d47d901a8d5ffd91743107a1"
},
{
"fixed": "eb02f218aacb36365e0ca2339cbae81fb05d31a5"
},
{
"fixed": "1436031b33fa23ab1ce7df5bc5500093413e8acf"
},
{
"fixed": "b885c7783c19c36c7bf899492a0bffcd68afa8c7"
},
{
"fixed": "89479a27fa4e1e11f378b3724944eabceb84f114"
},
{
"fixed": "aa807064473abd6f2cafe419fb77ea402d3e3104"
},
{
"fixed": "8b4468ec023d0d1b4669dfb867588997cc03a06b"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-68459.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "3.8.0"
},
{
"fixed": "5.15.212"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.178"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.145"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.96"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.39"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.1.5"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-68459.json"
}
}
],
"modified": "2026-10-28T02:30:26.438085806Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/1436031b33fa23ab1ce7df5bc5500093413e8acf",
"https://git.kernel.org/stable/c/8071500a8124e5a6d47d901a8d5ffd91743107a1",
"https://git.kernel.org/stable/c/89479a27fa4e1e11f378b3724944eabceb84f114",
"https://git.kernel.org/stable/c/8b4468ec023d0d1b4669dfb867588997cc03a06b",
"https://git.kernel.org/stable/c/aa807064473abd6f2cafe419fb77ea402d3e3104",
"https://git.kernel.org/stable/c/b885c7783c19c36c7bf899492a0bffcd68afa8c7",
"https://git.kernel.org/stable/c/eb02f218aacb36365e0ca2339cbae81fb05d31a5",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/68xxx/CVE-2026-68459.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-68459",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/68xxx/CVE-2026-68459.json"
}
},
"related_cves": [
{
"value": "CVE-2026-68459",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 493065,
"published_at": "2026-08-15T05:51:19.713+00:00"
}