Privileged local crash via stale F2FS inode
Published May 26, 2023 · Updated Oct 15, 2024
NULL pointer dereference in Linux kernel F2FS allows local users with filesystem administration privileges to crash the system. A resize/remount race can leave dirty metadata for writeback after f2fs_put_super clears node_inode, so f2fs_write_end_io dereferences the cleared pointer. Triggering the crash requires privileges to issue F2FS_IOC_RESIZE_FS and race a read-only remount; the demonstrated consequence is a kernel panic and service interruption.
Summary
What happened
NULL pointer dereference in Linux kernel F2FS allows local users with filesystem administration privileges to crash the system. A resize/remount race can leave dirty metadata for writeback after f2fs_put_super clears node_inode, so f2fs_write_end_io dereferences the cleared pointer. Triggering the crash requires privileges to issue F2FS_IOC_RESIZE_FS and race a read-only remount; the demonstrated consequence is a kernel panic and service interruption.
The record
- CVE
- CVE-2023-2898
- Published
- May 26, 2023
- Updated
- Oct 15, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 26, 2023CVE publishedPublication date reported by the CVE source.
- Oct 15, 2024Record 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=NA
What conditions does exploitation require?
What is affected?
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