CVE-2026-23234

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-03-04. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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(medium)
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

Advisory Details (8)

Auto-updated Aug 2, 2026
No patch confirmed yet.
generic

f2fs: fix to avoid UAF in f2fs_write_end_io() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cf4a9e1bc8129eb63fda5f8bdcd8d87f0bd76f42
generic

f2fs: fix to avoid UAF in f2fs_write_end_io() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ce2739e482bce8d2c014d76c4531c877f382aa54
generic

f2fs: fix to avoid UAF in f2fs_write_end_io() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/acc2c97fc0005846e5cf11b5ba3189fef130c9b3
generic

f2fs: fix to avoid UAF in f2fs_write_end_io() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a42f99be8a16b32a0bb91bb6dda212a6ad61be5d
generic

f2fs: fix to avoid UAF in f2fs_write_end_io() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/995030be4ce6338c6ff814583c14166446a64008
generic

f2fs: fix to avoid UAF in f2fs_write_end_io() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/505e1c0530db6152cab3feef8e3e4da3d3e358c9
generic

f2fs: fix to avoid UAF in f2fs_write_end_io() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2f67ff1e15a8a4d0e4ffc6564ab20d03d7398fe9
generic

f2fs: fix to avoid UAF in f2fs_write_end_io() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0fb58aff0dafd6837cc91f4154f3ed6e020358fa

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)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-07-27ubuntu
ubuntulinux-virtual-6.8 (6.8.0-134.134) @ noble2026-07-27ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1058.61.1) @ noble2026-07-27ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-134.134.1) @ noble2026-07-27ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-07-27ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-07-27ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-07-27ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-07-27ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-07-27ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-07-27ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-07-27ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-07-27ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-07-27ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-07-27ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-07-27ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-07-27ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-07-27ubuntu
linuxKernel @ 5.10.251—osv

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.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (49 versions)5.10.251-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.162-1~deb11u1 (15 versions)6.1.164-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (47 versions)6.1.164-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.74-2~bpo12+1 (15 versions)6.12.74-2—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (102 versions)6.18.13-1—

Weakness Classification(1)

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

All Vendor Advisories

(22)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 23× 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-09-19 12:32 UTCOSV refresh
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-16 14:07 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-12 15:01 UTCEPSS rescore
  7. 2026-09-11 14:52 UTCEPSS rescore
  8. 2026-09-10 09:34 UTCEPSS rescore
  9. 2026-09-08 22:00 UTCEPSS rescore
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-04 05:06 UTCEPSS rescore
  14. 2026-09-02 14:11 UTCEPSS rescore
  15. 2026-09-01 13:53 UTCEPSS rescore
  16. 2026-09-01 04:39 UTCEPSS rescore
  17. 2026-08-31 16:04 UTCOSV refresh
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-28 21:41 UTCEPSS rescore
  20. 2026-08-27 14:25 UTCEPSS rescore
  21. 2026-08-26 14:46 UTCEPSS rescore
  22. 2026-08-25 13:48 UTCEPSS rescore
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-19 17:03 UTCEPSS rescore
Show 57 more
  1. 2026-08-18 13:48 UTCEPSS rescore
  2. 2026-08-17 13:47 UTCEPSS rescore
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-16 02:14 UTCEPSS rescore
  5. 2026-08-15 01:30 UTCEPSS rescore
  6. 2026-08-14 20:57 UTCVendor advisory
  7. 2026-08-14 20:57 UTCGHSA enrichment
  8. 2026-08-14 08:37 UTCEG score recompute
  9. 2026-08-14 08:37 UTCVendor advisory
  10. 2026-08-14 08:37 UTCGHSA enrichment
  11. 2026-08-13 22:00 UTCEPSS rescore
  12. 2026-08-13 00:24 UTCEG score recompute
  13. 2026-08-13 00:24 UTCVendor advisory
  14. 2026-08-13 00:24 UTCGHSA enrichment
  15. 2026-08-12 13:50 UTCEPSS rescore
  16. 2026-08-11 23:18 UTCEG score recompute
  17. 2026-08-11 23:18 UTCVendor advisory
  18. 2026-08-11 23:18 UTCGHSA enrichment
  19. 2026-08-11 13:42 UTCEPSS rescore
  20. 2026-08-11 05:52 UTCEG score recompute
  21. 2026-08-11 05:52 UTCVendor advisory
  22. 2026-08-11 05:52 UTCGHSA enrichment
  23. 2026-08-11 00:00 UTCEPSS rescore
  24. 2026-08-10 08:19 UTCVendor advisory
  25. 2026-08-10 08:19 UTCGHSA enrichment
  26. 2026-08-09 20:15 UTCVendor advisory
  27. 2026-08-09 20:15 UTCGHSA enrichment
  28. 2026-08-09 08:14 UTCEG score recompute
  29. 2026-08-09 08:14 UTCVendor advisory
  30. 2026-08-09 08:14 UTCGHSA enrichment
  31. 2026-08-08 16:37 UTCEPSS rescore
  32. 2026-08-08 08:08 UTCVendor advisory
  33. 2026-08-08 08:08 UTCGHSA enrichment
  34. 2026-08-07 20:07 UTCEG score recompute
  35. 2026-08-07 20:07 UTCVendor advisory
  36. 2026-08-07 20:07 UTCGHSA enrichment
  37. 2026-08-06 13:46 UTCEPSS rescore
  38. 2026-08-06 02:42 UTCEG score recompute
  39. 2026-08-06 02:42 UTCVendor advisory
  40. 2026-08-06 02:42 UTCGHSA enrichment
  41. 2026-08-05 19:17 UTCEPSS rescore
  42. 2026-08-04 10:38 UTCEPSS rescore
  43. 2026-08-04 04:11 UTCEG score recompute
  44. 2026-08-04 04:11 UTCVendor advisory
  45. 2026-08-04 04:11 UTCGHSA enrichment
  46. 2026-08-03 10:35 UTCEPSS rescore
  47. 2026-08-02 19:01 UTCEG score recompute
  48. 2026-08-02 19:01 UTCVendor advisory
  49. 2026-08-02 19:01 UTCGHSA enrichment
  50. 2026-08-02 02:26 UTCEPSS rescore
  51. 2026-08-01 04:15 UTCEPSS rescore
  52. 2026-07-30 01:30 UTCEPSS rescore
  53. 2026-07-27 14:13 UTCEPSS rescore
  54. 2026-07-27 12:56 UTCEG score recompute
  55. 2026-07-27 12:56 UTCVendor advisory
  56. 2026-07-27 12:56 UTCGHSA enrichment
  57. 2026-07-27 12:50 UTCOSV refresh

Related CVEs(same product + same vendor + same CWE)

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 98.0% 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

See which npm, PyPI, Go, and Maven packages are affected by 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.

Start Free Scan →Browse All CVEs