Local kernel memory corruption via stale f2fs iterator
Published Feb 26, 2025 · Updated Aug 5, 2026
Memory corruption in the f2fs subsystem in Linux allows local users to gain kernel read and write primitives through atomic-write ioctls. The f2fs_drop_inmem_page path leaves cur as a bogus pointer when no list entry matches, then reads cur->page and can pass the stale object to list_del and kmem_cache_free. A low-privileged user must own a file on a mounted f2fs volume and drive an atomic-write, write, and truncate sequence, which can corrupt kernel heap state or panic the host.
Summary
What happened
Memory corruption in the f2fs subsystem in Linux allows local users to gain kernel read and write primitives through atomic-write ioctls. The f2fs_drop_inmem_page path leaves cur as a bogus pointer when no list entry matches, then reads cur->page and can pass the stale object to list_del and kmem_cache_free. A low-privileged user must own a file on a mounted f2fs volume and drive an atomic-write, write, and truncate sequence, which can corrupt kernel heap state or panic the host.
The record
- CVE
- CVE-2022-49425
- Published
- Feb 26, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 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.12
- Affected versionversion=8c242db9b8c01b252290e23827163787f07e01d1 <2aaf51dd39afb6d01d13f1e6fe20b684733b37d5
- Affected versionversion=8c242db9b8c01b252290e23827163787f07e01d1 <385edd3ce5b4b1e9d31f474a5e35a39779ec1110
- Affected versionversion=8c242db9b8c01b252290e23827163787f07e01d1 <45b2b7d7108ae1e25a5036cab04ab9273e792332
- Affected versionversion=8c242db9b8c01b252290e23827163787f07e01d1 <51d584704d18e60fa473823654f35611c777b291
- Affected versionversion=8c242db9b8c01b252290e23827163787f07e01d1 <5e47a7add3dda7f236548c5ec3017776dc2a729f
- Affected versionversion=8c242db9b8c01b252290e23827163787f07e01d1 <b26e1c777890e4b938136deb8ec07a29f33862e4
- Affected versionversion=8c242db9b8c01b252290e23827163787f07e01d1 <ed7efc472c00986dcd6903ab6ed165c7fa167674
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