Kernel crash via dirty F2FS root inode
Published Dec 27, 2024 · Updated May 11, 2026
Denial of service in the Linux kernel F2FS implementation allows local users to crash the kernel during filesystem unmount. After checkpoint-disabled file creation exhausts free segments, f2fs_enable_checkpoint leaves the root inode dirty when writeback fails, and f2fs_evict_inode triggers BUG_ON during unmount. Reaching the fault requires local access to mount and remount an F2FS filesystem, disable and re-enable checkpointing, exhaust its free space, and then unmount it; the bounded consequence is a kernel crash.
Summary
What happened
Denial of service in the Linux kernel F2FS implementation allows local users to crash the kernel during filesystem unmount. After checkpoint-disabled file creation exhausts free segments, f2fs_enable_checkpoint leaves the root inode dirty when writeback fails, and f2fs_evict_inode triggers BUG_ON during unmount. Reaching the fault requires local access to mount and remount an F2FS filesystem, disable and re-enable checkpointing, exhaust its free space, and then unmount it; the bounded consequence is a kernel crash.
The record
- CVE
- CVE-2024-56586
- Published
- Dec 27, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 27, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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.8
- Affected versionversion=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <9669b28f81e0ec6305af7773846fbe2cef1e7d61
- Affected versionversion=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <9e28513fd2858911dcf47b84160a8824587536b6
- Affected versionversion=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <a365de2fbfbe1e6740bfb75ab5c3245cf7bbe4d7
- Affected versionversion=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <ac8aaf78bd039fa1be0acaa8e84a56499f79d721
- Affected versionversion=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <d5c367ef8287fb4d235c46a2f8c8d68715f3a0ca
- Affected versionversion=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <dff561e4060d28edc9a2960d4a87f3c945a96aa3
- Affected versionversion=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <ef517d2d21c3d8e2ad35b2bb728bd1c90a31e617
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