Kernel crash via unlocked inline-data layout transition
Published Dec 16, 2025 · Updated Dec 16, 2025
Race condition in Linux ext4 allows local users to crash the kernel by racing inline-data destruction against block mapping operations. ext4_destroy_inline_data_nolock changes inode layout flags without holding i_data_sem, so ext4_map_blocks can select the indirect mapper while the inode already carries the extents flag. Concurrent filesystem operations on an ext4 inode with inline data are required, and successful triggering interrupts the host through a kernel BUG assertion.
Summary
What happened
Race condition in Linux ext4 allows local users to crash the kernel by racing inline-data destruction against block mapping operations. ext4_destroy_inline_data_nolock changes inode layout flags without holding i_data_sem, so ext4_map_blocks can select the indirect mapper while the inode already carries the extents flag. Concurrent filesystem operations on an ext4 inode with inline data are required, and successful triggering interrupts the host through a kernel BUG assertion.
The record
- CVE
- CVE-2025-68261
- Published
- Dec 16, 2025
- Updated
- Dec 16, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-367, T1489
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 16, 2025CVE publishedPublication date reported by the CVE source.
- Dec 16, 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=3e96c3fdcfccb321a9e1623f78cc71b44593e965
- Affected versionversion=4.11
- Affected versionversion=5781ac24bbd998ebb1ff30143bb06244d847af48
- Affected versionversion=7cf6b709b6412afd1d93b2c4b37163c3602e3b95
- Affected versionversion=9b06cce3ca4d60d442c39bfa7c058b71b1cee6c2
- Affected versionversion=c755e251357a0cee0679081f08c3f4ba797a8009 <0cd8feea8777f8d9b9a862b89c688b049a5c8475
- Affected versionversion=c755e251357a0cee0679081f08c3f4ba797a8009 <22a76b0861ae61a299c8e126c1aca8c4fda820fd
- Affected versionversion=c755e251357a0cee0679081f08c3f4ba797a8009 <5cad18e527ba8a9ca5463cc170073eeb5a4826f4
- Affected versionversion=c755e251357a0cee0679081f08c3f4ba797a8009 <ba8aeff294ac7ff6dfe293663d815c54c5ee218c
- Affected versionversion=da1e40237f8f3516581b534c484c236a79ccfd14
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