Kernel memory corruption via F2FS unmount race
Published Mar 4, 2026 · Updated Mar 4, 2026
Use-after-free in the F2FS write-completion path in Linux Kernel allows local users to access freed kernel memory during concurrent I/O and unmount. f2fs_write_end_io() ends folio writeback before waking the checkpoint thread, allowing f2fs_put_super() to free superblock state before get_pages() reads it. The race requires CAP_SYS_ADMIN in the initial user namespace, an F2FS-capable block device, and concurrent unmount activity; successful exploitation reads or modifies kernel memory or crashes the system.
Summary
What happened
Use-after-free in the F2FS write-completion path in Linux Kernel allows local users to access freed kernel memory during concurrent I/O and unmount. f2fs_write_end_io() ends folio writeback before waking the checkpoint thread, allowing f2fs_put_super() to free superblock state before get_pages() reads it. The race requires CAP_SYS_ADMIN in the initial user namespace, an F2FS-capable block device, and concurrent unmount activity; successful exploitation reads or modifies kernel memory or crashes the system.
The record
- CVE
- CVE-2026-23234
- Published
- Mar 4, 2026
- Updated
- Mar 4, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1499
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Mar 4, 2026CVE publishedPublication date reported by the CVE source.
- Mar 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.13
- Affected versionversion=e234088758fca3a669ebb1a02d8bf7bf60f0e4ff <0fb58aff0dafd6837cc91f4154f3ed6e020358fa
- Affected versionversion=e234088758fca3a669ebb1a02d8bf7bf60f0e4ff <2f67ff1e15a8a4d0e4ffc6564ab20d03d7398fe9
- Affected versionversion=e234088758fca3a669ebb1a02d8bf7bf60f0e4ff <505e1c0530db6152cab3feef8e3e4da3d3e358c9
- Affected versionversion=e234088758fca3a669ebb1a02d8bf7bf60f0e4ff <995030be4ce6338c6ff814583c14166446a64008
- Affected versionversion=e234088758fca3a669ebb1a02d8bf7bf60f0e4ff <a42f99be8a16b32a0bb91bb6dda212a6ad61be5d
- Affected versionversion=e234088758fca3a669ebb1a02d8bf7bf60f0e4ff <acc2c97fc0005846e5cf11b5ba3189fef130c9b3
- Affected versionversion=e234088758fca3a669ebb1a02d8bf7bf60f0e4ff <ce2739e482bce8d2c014d76c4531c877f382aa54
- Affected versionversion=e234088758fca3a669ebb1a02d8bf7bf60f0e4ff <cf4a9e1bc8129eb63fda5f8bdcd8d87f0bd76f42
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo