CVE-2026-68459: f2fs: fix potential deadlock in gc_merge path of f2fs_balance_fs()
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 1436031b33fa23ab1ce7df5bc5500093413e8acf, 8071500a8124e5a6d47d901a8d5ffd91743107a1, 89479a27fa4e1e11f378b3724944eabceb84f114.
Low priority for now. Upgrade to Linux Linux 1436031b33fa23ab1ce7df5bc5500093413e8acf, 8071500a8124e5a6d47d901a8d5ffd91743107a1, 89479a27fa4e1e11f378b3724944eabceb84f114 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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);
- Published
- Aug 15, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.8affected
- 351df4b201157351c7d26bf12c3eeb9dbce98854 and later · before 8071500a8124e5a6d47d901a8d5ffd91743107a1affected · git
- 351df4b201157351c7d26bf12c3eeb9dbce98854 and later · before eb02f218aacb36365e0ca2339cbae81fb05d31a5affected · git
- 351df4b201157351c7d26bf12c3eeb9dbce98854 and later · before 1436031b33fa23ab1ce7df5bc5500093413e8acfaffected · git
- 351df4b201157351c7d26bf12c3eeb9dbce98854 and later · before b885c7783c19c36c7bf899492a0bffcd68afa8c7affected · git
- 351df4b201157351c7d26bf12c3eeb9dbce98854 and later · before 89479a27fa4e1e11f378b3724944eabceb84f114affected · git
- 351df4b201157351c7d26bf12c3eeb9dbce98854 and later · before aa807064473abd6f2cafe419fb77ea402d3e3104affected · git
- 351df4b201157351c7d26bf12c3eeb9dbce98854 and later · before 8b4468ec023d0d1b4669dfb867588997cc03a06baffected · git
- before 3.8not affected · semver
- 5.15.212 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.96-1 | 6.12.96-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-68457Aug 15, 2026 · ksmbd: use opener credentials for FSCTL mutations36Monitor
- ← EarlierCVE-2026-68458Aug 15, 2026 · binder: cache secctx size before release zeroes it31Monitor
- Later →CVE-2026-68460Aug 15, 2026 · f2fs: fix potential deadlock in f2fs_balance_fs()0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1436031b33fa23ab1ce7df5bc5500093413e8acf | Vendor (CNA) |
| Linux Linux | 8071500a8124e5a6d47d901a8d5ffd91743107a1 | Vendor (CNA) |
| Linux Linux | 89479a27fa4e1e11f378b3724944eabceb84f114 | Vendor (CNA) |
| Linux Linux | 8b4468ec023d0d1b4669dfb867588997cc03a06b | Vendor (CNA) |
| Linux Linux | aa807064473abd6f2cafe419fb77ea402d3e3104 | Vendor (CNA) |
| Linux Linux | b885c7783c19c36c7bf899492a0bffcd68afa8c7 | Vendor (CNA) |
| Linux Linux | eb02f218aacb36365e0ca2339cbae81fb05d31a5 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/8071500a8124e5a6d47d901a8d5ffd91743107a1
- git.kernel.org/stable/c/89479a27fa4e1e11f378b3724944eabceb84f114
- git.kernel.org/stable/c/8b4468ec023d0d1b4669dfb867588997cc03a06b
- git.kernel.org/stable/c/aa807064473abd6f2cafe419fb77ea402d3e3104
- git.kernel.org/stable/c/b885c7783c19c36c7bf899492a0bffcd68afa8c7
- git.kernel.org/stable/c/eb02f218aacb36365e0ca2339cbae81fb05d31a5
Vendor advisories and official records. Exploit/PoC links are deliberately left out.