CVE Catalog

CVE-2025-40167

HighCVSS 7.8
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.15%

5th percentile - higher than 5% of all known CVEs

Summary

In the Linux kernel's ext4 filesystem, there is no validation for an invalid combination of INLINE_DATA and EXTENTS flags in an inode. This combination can lead to a BUG_ON in ext4_es_cache_extent() due to integer underflow.

Risk Assessment

Opening a corrupted ext4 filesystem can cause a kernel crash (BUG_ON), leading to denial of service (DoS).

Recommendation

Apply the Linux kernel patch that adds early detection of the invalid INLINE_DATA and EXTENTS flag combination in ext4_iget() and rejects corrupted inodes.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

In the Linux kernel, the following vulnerability has been resolved: ext4: detect invalid INLINE_DATA + EXTENTS flag combination syzbot reported a BUG_ON in ext4_es_cache_extent() when opening a verity file on a corrupted ext4 filesystem mounted without a journal. The issue is that the filesystem has an inode with both the INLINE_DATA and EXTENTS flags set: EXT4-fs error (device loop0): ext4_cache_extents:545: inode #15: comm syz.0.17: corrupted extent tree: lblk 0 < prev 66 Investigation revealed that the inode has both flags set: DEBUG: inode 15 - flag=1, i_inline_off=164, has_inline=1, extents_flag=1 This is an invalid combination since an inode should have either: - INLINE_DATA: data stored directly in the inode - EXTENTS: data stored in extent-mapped blocks Having both flags causes ext4_has_inline_data() to return true, skipping extent tree validation in __ext4_iget(). The unvalidated out-of-order extents then trigger a BUG_ON in ext4_es_cache_extent() due to integer underflow when calculating hole sizes. Fix this by detecting this invalid flag combination early in ext4_iget() and rejecting the corrupted inode.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS