Filesystem mount denial via atomic checkpoint race
Published Mar 18, 2026 · Updated Mar 18, 2026
Race condition in Linux Kernel F2FS allows local users to prevent filesystem mounting after an abrupt power loss. A missing node_write read lock lets an atomic fsync rewrite a node folio after a concurrent checkpoint has already marked its NAT entry as checkpointed, leaving recovery metadata inconsistent. Triggering the failure requires an atomic file commit to overlap a checkpoint and then an abrupt power loss; the resulting reboot can fail to mount the affected F2FS filesystem with -EINVAL.
Summary
What happened
Race condition in Linux Kernel F2FS allows local users to prevent filesystem mounting after an abrupt power loss. A missing node_write read lock lets an atomic fsync rewrite a node folio after a concurrent checkpoint has already marked its NAT entry as checkpointed, leaving recovery metadata inconsistent. Triggering the failure requires an atomic file commit to overlap a checkpoint and then an abrupt power loss; the resulting reboot can fail to mount the affected F2FS filesystem with -EINVAL.
The record
- CVE
- CVE-2026-23267
- Published
- Mar 18, 2026
- Updated
- Mar 18, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 18, 2026CVE publishedPublication date reported by the CVE source.
- Mar 18, 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=4.7
- Affected versionversion=608514deba38c8611ad330d6a3c8e2b9a1f68e4b <32bc3c9fe18881d50dd51fd5f26d19fe1190dc0d
- Affected versionversion=608514deba38c8611ad330d6a3c8e2b9a1f68e4b <75e19da068adf0dc5dd269dd157392434b9117d4
- Affected versionversion=608514deba38c8611ad330d6a3c8e2b9a1f68e4b <7633a7387eb4d0259d6bea945e1d3469cd135bbc
- Affected versionversion=608514deba38c8611ad330d6a3c8e2b9a1f68e4b <962c167b0f262b9962207fbeaa531721d55ea00e
- Affected versionversion=608514deba38c8611ad330d6a3c8e2b9a1f68e4b <bd66b4c487d5091d2a65d6089e0de36f0c26a4c7
- Affected versionversion=608514deba38c8611ad330d6a3c8e2b9a1f68e4b <ed81bc5885460905f9160e7b463e5708fd056324
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.
Weakness, pattern, technique
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