Kernel panic via corrupted F2FS validity counters
Published Feb 26, 2025 · Updated Aug 15, 2026
Denial of service in the Linux kernel's F2FS implementation allows local users to trigger a kernel panic through a crafted filesystem. When corrupted total-valid-block or total-valid-node counters reach zero, dec_valid_node_count() decrements them and invokes f2fs_bug_on() instead of flagging the filesystem for checking. Reachability requires local access to exercise inode removal or eviction on an affected F2FS mount; the documented consequence is a host-wide kernel panic.
Summary
What happened
Denial of service in the Linux kernel's F2FS implementation allows local users to trigger a kernel panic through a crafted filesystem. When corrupted total-valid-block or total-valid-node counters reach zero, dec_valid_node_count() decrements them and invokes f2fs_bug_on() instead of flagging the filesystem for checking. Reachability requires local access to exercise inode removal or eviction on an affected F2FS mount; the documented consequence is a host-wide kernel panic.
The record
- CVE
- CVE-2022-49380
- Published
- Feb 26, 2025
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 2025CVE publishedPublication date reported by the CVE source.
- Aug 15, 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=39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 <2766ddaf45b69252bb8fe526b5b6e56904a9ae7a
- Affected versionversion=39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 <4d17e6fe9293d57081ffdc11e1cf313e25e8fd9e
- Affected versionversion=39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 <89d9a48d0cd30429463ea4e37ca83be6773ed5eb
- Affected versionversion=39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 <bce859358d3d5940aa858e40ceee70ee6e76130e
- Affected versionversion=39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 <ccffa99ae6a1f44797b57444c6a80382a42928fe
- Affected versionversion=39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 <f8b3c3fcf33105bc1ee7788e3b51b0a1ae42ae53
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