Kernel crash via F2FS extent-tree race
Published May 28, 2026 · Updated May 28, 2026
Race condition in Linux Kernel F2FS affected releases allows local users to crash the kernel during concurrent inode teardown and writeback. f2fs_destroy_extent_node() clears an extent tree without first setting FI_NO_EXTENT, so writeback can add a node before __destroy_extent_node() verifies node_cnt. Triggering the failure requires an F2FS inode drop with I_SYNC while a kworker updates the same read or block-age extent tree; the reported consequence is a kernel BUG and service interruption.
Summary
What happened
Race condition in Linux Kernel F2FS affected releases allows local users to crash the kernel during concurrent inode teardown and writeback. f2fs_destroy_extent_node() clears an extent tree without first setting FI_NO_EXTENT, so writeback can add a node before __destroy_extent_node() verifies node_cnt. Triggering the failure requires an F2FS inode drop with I_SYNC while a kworker updates the same read or block-age extent tree; the reported consequence is a kernel BUG and service interruption.
The record
- CVE
- CVE-2026-46194
- Published
- May 28, 2026
- Updated
- May 28, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-367, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 28, 2026CVE publishedPublication date reported by the CVE source.
- May 28, 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=295b50e95e900da31ff237e46e04525fa799b2cf <42dd1c91f993431d0b399502479d00e6ad1bca71
- Affected versionversion=3fc5d5a182f6a1f8bd4dc775feb54c369dd2c343 <0559a0e962aacbb47519e26ee663be04b72dcb92
- Affected versionversion=3fc5d5a182f6a1f8bd4dc775feb54c369dd2c343 <b0e4395870eb3441ddc959f6710b5f6ca61aff26
- Affected versionversion=3fc5d5a182f6a1f8bd4dc775feb54c369dd2c343 <ed78aeebef05212ef7dca93bd931e4eff67c113f
- Affected versionversion=6.12.5 <6.12.88
- Affected versionversion=6.13
- Affected versionversion=6.6.66 <6.6.140
- Affected versionversion=924f7dd1e832e4e4530d14711db223d2803f7b61 <ab1eaf9d5c99042f5b0243bf67a06283a4c0757f
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