Kernel memory corruption via premature F2FS teardown
Published Dec 24, 2025 · Updated Dec 24, 2025
Use-after-free in the Linux kernel F2FS implementation allows local users to corrupt kernel memory or crash the system during unmount. When cp_error is set, f2fs_wait_on_all_pages stops before checkpoint-data writeback drains, allowing F2FS teardown while pending I/O still references freed filesystem state. Reachability requires write access to an F2FS mount, outstanding dirty pages, and a metadata or backing-device error; affected CHECK_FS builds panic at unmount.
Summary
What happened
Use-after-free in the Linux kernel F2FS implementation allows local users to corrupt kernel memory or crash the system during unmount. When cp_error is set, f2fs_wait_on_all_pages stops before checkpoint-data writeback drains, allowing F2FS teardown while pending I/O still references freed filesystem state. Reachability requires write access to an F2FS mount, outstanding dirty pages, and a metadata or backing-device error; affected CHECK_FS builds panic at unmount.
The record
- CVE
- CVE-2023-54124
- Published
- Dec 24, 2025
- Updated
- Dec 24, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1068
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 24, 2025CVE publishedPublication date reported by the CVE source.
- Dec 24, 2025Record 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4ceedc2f8bdffb82e40b7d1bb912304f8e157cb1
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7741ddc882a0c806a6508ba8203c55a779db7a21
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <82c3d6e9db41cbd3af1d4f90bdb441740b5fad10
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <92575f05a32dafb16348bfa5e62478118a9be069
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ad87bd313f70b51e48019d5ce2d02d73152356b3
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c9b3649a934d131151111354bcbb638076f03a30
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d8f4ad5f3979dbd8e6251259562f12472717883a
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