CVE-2026-68459

UNRATEDCVSS · not yet scoredTrending — 5 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

References (7)

Vendor Advisories for CVE-2026-68459(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 16× in last 7d / 16× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 10:57 UTCGHSA enrichment
  3. 2026-08-19 17:04 UTCEPSS rescore
  4. 2026-08-18 13:49 UTCEPSS rescore
  5. 2026-08-18 13:49 UTCEPSS rescore
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-17 06:30 UTCGHSA enrichment
  8. 2026-08-17 06:18 UTCNVD update
  9. 2026-08-17 05:35 UTCEG score recompute
  10. 2026-08-17 05:35 UTCGHSA enrichment
  11. 2026-08-17 05:25 UTCMITRE cvelistV5
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-15 06:20 UTCNVD update
  15. 2026-08-15 06:20 UTCEG score recompute
  16. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-68459?
CVE-2026-68459 is a publicly disclosed vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: f2fs: fix potential deadlock in gcmerge path of f2fsbalance_fs() When we mount device w/ gc_merge mount option, we may suffer below potential deadlock: Kworker GC trehad Truncator f2fswritecache_pages f2fswritesingledatapage…
When was CVE-2026-68459 disclosed?
CVE-2026-68459 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68459 actively exploited?
CVE-2026-68459 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.0% of all scored CVEs.
How do I remediate CVE-2026-68459?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68459, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-68459

Explore →

Is Your Infrastructure Affected by CVE-2026-68459?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs