Kernel crash via ext4 inline-data conversion race
Published Feb 26, 2025 · Updated May 11, 2026
Race condition in the Linux kernel ext4 filesystem allows local users to crash the kernel through concurrent write and fallocate operations. ext4_convert_inline_data uses xattr_sem while generic_perform_write uses i_rwsem, allowing inline-data state to change between checks and leaving a null journal handle. Triggering the race requires write access to an ext4 inode with inline data and concurrent write and fallocate activity; the resulting metadata inconsistency reaches BUG_ON and interrupts the system.
Summary
What happened
Race condition in the Linux kernel ext4 filesystem allows local users to crash the kernel through concurrent write and fallocate operations. ext4_convert_inline_data uses xattr_sem while generic_perform_write uses i_rwsem, allowing inline-data state to change between checks and leaving a null journal handle. Triggering the race requires write access to an ext4 inode with inline data and concurrent write and fallocate activity; the resulting metadata inconsistency reaches BUG_ON and interrupts the system.
The record
- CVE
- CVE-2022-49414
- Published
- Feb 26, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-362, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 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=0c8d414f163f5d35e43a4de7a6e5ee8c253fcccf <14602353b350950b551eccc6b46411aa3b12ffe2
- Affected versionversion=0c8d414f163f5d35e43a4de7a6e5ee8c253fcccf <18881d7e517169193d9ef6c89c7f322e3e164277
- Affected versionversion=0c8d414f163f5d35e43a4de7a6e5ee8c253fcccf <725e00cb7039eae291890f1bb19bc867176745f6
- Affected versionversion=0c8d414f163f5d35e43a4de7a6e5ee8c253fcccf <91f90b571f1a23f5b8a9c2b68a9aa5d6981a3c3d
- Affected versionversion=0c8d414f163f5d35e43a4de7a6e5ee8c253fcccf <ccc6639f831bee91aa8b41c8a1cdd020ecfb9f32
- Affected versionversion=0c8d414f163f5d35e43a4de7a6e5ee8c253fcccf <f87c7a4b084afc13190cbb263538e444cb2b392a
- Affected versionversion=3.8
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