CVE-2025-40167
Last modified
CVE-2025-40167 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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.. EPSS estimates a 0.19% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= f19d5870cbf72d4cb2a8e1f749dff97af99b071e, < 4954d297c91d292630ab43ba4d195dc371ce65d3; >= f19d5870cbf72d4cb2a8e1f749dff97af99b071e, < f061f7c331fc16250fc82aa68964f35821687217; >= f19d5870cbf72d4cb2a8e1f749dff97af99b071e, < 2e9e10657b04152ed0d6ecae8d0c02a3405e28f5; >= f19d5870cbf72d4cb2a8e1f749dff97af99b071e, < 1437c95ab2a28b138d4521653583729f61ccb48b; >= f19d5870cbf72d4cb2a8e1f749dff97af99b071e, < cb6039b68efa547b676a8a10fc4618d9d1865c23; >= f19d5870cbf72d4cb2a8e1f749dff97af99b071e, < de985264eef64be8a90595908f2e6a87946dad34; >= f19d5870cbf72d4cb2a8e1f749dff97af99b071e, < 1f5ccd22ff482639133f2a0fe08f6d19d0e68717; >= f19d5870cbf72d4cb2a8e1f749dff97af99b071e, < 1d3ad183943b38eec2acf72a0ae98e635dc8456b |
| Linux | Linux | 3.8 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2025-40167?
How severe is CVE-2025-40167?
How do I fix CVE-2025-40167?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-40161In the Linux kernel, the following vulnerability has been re…
- CVE-2025-40162In the Linux kernel, the following vulnerability has been re…
- CVE-2025-40163In the Linux kernel, the following vulnerability has been re…
- CVE-2025-40164In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-40165In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-40166In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-40168In the Linux kernel, the following vulnerability has been re…8.1
- CVE-2025-40169In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-4017A vulnerability classified as problematic was found in 20120…6.5
- CVE-2025-40170In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-40171In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2025-40172In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2025-40167?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
