Kernel panic via unchecked recovery block address
Published Sep 15, 2025 · Updated Sep 15, 2025
Improper validation in Linux F2FS allows local users to trigger a kernel panic by mounting a crafted filesystem image. During fsync-data recovery, do_recover_data accepts a destination block address whose SIT allocation state conflicts with the inode mapping, then calls f2fs_replace_block and updates the inconsistent SIT bitmap. A local user must be able to supply and mount the malformed image; kernels built with CONFIG_F2FS_CHECK_FS panic, while other builds emit a warning during recovery.
Summary
What happened
Improper validation in Linux F2FS allows local users to trigger a kernel panic by mounting a crafted filesystem image. During fsync-data recovery, do_recover_data accepts a destination block address whose SIT allocation state conflicts with the inode mapping, then calls f2fs_replace_block and updates the inconsistent SIT bitmap. A local user must be able to supply and mount the malformed image; kernels built with CONFIG_F2FS_CHECK_FS panic, while other builds emit a warning during recovery.
The record
- CVE
- CVE-2022-50273
- Published
- Sep 15, 2025
- Updated
- Sep 15, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 15, 2025CVE publishedPublication date reported by the CVE source.
- Sep 15, 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 <0ef4ca04a3f9223ff8bc440041c524b2123e09a3
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3a4d24d746866dd45d970bd565ff3886e839366a
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <68b1e607559d3dc85f94b0d738d7c4e8029b0cfa
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <73fb4bd2c055a393816f078f158cdd3025006f1d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8f0a47def4722c5fd8d6b9268b5ffed8a249e2db
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ed854f10e6afd5cbd5c3274d4c4df4bfe0ab4362
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