CVE-2026-23234

HIGHNVD 7.87.8
EchelonGraph scoreLOW confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-03-04.

Triggered by: GitHub Security Advisory CVSS
Sources: ghsa
Trending — 5 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

f2fs: fix to avoid UAF in f2fs_write_end_io()

As syzbot reported an use-after-free issue in f2fs_write_end_io().

It is caused by below race condition:

loop device umount

  • worker_thread
  • loop_process_work
  • do_req_filebacked
  • lo_rw_aio
  • lo_rw_aio_complete
  • blk_mq_end_request
  • blk_update_request
  • f2fs_write_end_io
  • dec_page_count
  • folio_end_writeback
  • kill_f2fs_super
  • kill_block_super
  • f2fs_put_super
: free(sbi) : get_pages(, F2FS_WB_CP_DATA) accessed sbi which is freed

In kill_f2fs_super(), we will drop all page caches of f2fs inodes before call free(sbi), it guarantee that all folios should end its writeback, so it should be safe to access sbi before last folio_end_writeback().

Let's relocate ckpt thread wakeup flow before folio_end_writeback() to resolve this issue.

CVSS v3
7.8
EG Score
7.8(low)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

March 4, 2026

Last Modified

June 17, 2026

Vendor Advisories for CVE-2026-23234(1)

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

Patch Availability(18)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(17)

Data Freshness Timeline

(refreshed 5× in last 7d / 5× 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-07-27 14:13 UTCEPSS rescore
  2. 2026-07-27 12:56 UTCEG score recompute
  3. 2026-07-27 12:56 UTCVendor advisory
  4. 2026-07-27 12:56 UTCGHSA enrichment
  5. 2026-07-27 12:50 UTCOSV refresh

Frequently asked(5)

What is CVE-2026-23234?
CVE-2026-23234 is a high vulnerability published on March 4, 2026. In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid UAF in f2fswriteend_io() As syzbot reported an use-after-free issue in f2fswriteend_io(). It is caused by below race condition: loop device umount worker_thread loopprocesswork doreqfilebacked lorwaio -…
When was CVE-2026-23234 disclosed?
CVE-2026-23234 was first published in the National Vulnerability Database on March 4, 2026, with the most recent update on June 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-23234 actively exploited?
CVE-2026-23234 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 97.9% of all scored CVEs.
What is the CVSS score of CVE-2026-23234?
CVE-2026-23234 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-23234?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23234, 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-23234

Explore →

Is Your Infrastructure Affected by CVE-2026-23234?

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