Vulnerability · Published Nov 12, 2025 · Assigned by Linux

CVE-2025-40167ext4: detect invalid INLINE_DATA + EXTENTS flag combination

High 7.8

In plain English

A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 6% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.8High
Exploit odds (30 days)0.2%top 94.2% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official 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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.158-1DEBIAN-CVE-2025-40167
Debian:13linux6.12.57-1DEBIAN-CVE-2025-40167
Debian:14linux6.17.6-1DEBIAN-CVE-2025-40167
Ubuntu:22.04:LTSlinux5.15.0-170.180UBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux6.8.0-106.106UBUNTU-CVE-2025-40167
Ubuntu:25.10linux6.17.0-14.14UBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-aws5.15.0-1100.107UBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-aws6.8.0-1050.53UBUNTU-CVE-2025-40167
Ubuntu:25.10linux-aws6.17.0-1007.7UBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-aws-6.176.17.0-1007.7~24.04.1UBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-aws-6.86.8.0-1050.53~22.04.1UBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-azure5.15.0-1109.118UBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-azure6.8.0-1051.57UBUNTU-CVE-2025-40167
Ubuntu:25.10linux-azure6.17.0-1008.8UBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-azure-6.86.8.0-1051.57~22.04.1UBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1109.118.1UBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-azure-fde6.8.0-1058.65UBUNTU-CVE-2025-40167
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-azure-fde-6.86.8.0-1058.65~22.04.1UBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-gcp5.15.0-1100.109UBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-gcp6.8.0-1052.55UBUNTU-CVE-2025-40167
Ubuntu:25.10linux-gcp6.17.0-1007.7UBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-gcp-6.176.17.0-1008.8~24.04.1UBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-gcp-6.86.8.0-1052.55~22.04.1UBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-gke5.15.0-1096.102UBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-gke6.8.0-1048.53UBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1083.91UBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1035.38UBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-hwe-6.86.8.0-106.106~22.04.1UBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-ibm5.15.0-1094.97UBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-ibm6.8.0-1049.49UBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-ibm-6.86.8.0-1049.49~22.04.1UBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1095.101UBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-kvm5.15.0-1092.97UBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-170.180UBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-106.106.1UBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.86.8.0-106.106.1~22.04.1UBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1095.96UBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-nvidia6.8.0-1049.52UBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-nvidia-6.176.17.0-1008.8UBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-nvidia-6.86.8.0-1049.52~22.04.1UBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-nvidia-lowlatency6.8.0-1049.52.1UBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1052.52UBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1020.20UBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1041.41UBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-oem-6.176.17.0-1011.11UBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-oracle5.15.0-1097.103UBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-oracle6.8.0-1047.48UBUNTU-CVE-2025-40167
Ubuntu:25.10linux-oracle6.17.0-1007.7UBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-oracle-6.176.17.0-1007.7~24.04.1UBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-oracle-6.86.8.0-1047.48~22.04.1UBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-raspi5.15.0-1097.100UBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-raspi6.8.0-1050.54UBUNTU-CVE-2025-40167
Ubuntu:25.10linux-raspi6.17.0-1008.8UBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-40167
Ubuntu:25.10linux-realtime6.17.0-1006.7UBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-40167
Ubuntu:25.10linux-riscv6.17.0-14.14.1UBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-riscv-6.86.8.0-106.106~22.04.1UBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2025-40167
Ubuntu:24.04:LTSlinux-xilinx6.8.0-1028.29UBUNTU-CVE-2025-40167
Ubuntu:22.04:LTSlinux-xilinx-zynqmp5.15.0-1064.68UBUNTU-CVE-2025-40167

Affected products (as reported)

VendorProductVersions
Linux Linux f19d5870cbf72d4cb2a8e1f749dff97af99b071e – before 4954d297c91d292630ab43ba4d195dc371ce65d3f19d5870cbf72d4cb2a8e1f749dff97af99b071e – before f061f7c331fc16250fc82aa68964f35821687217f19d5870cbf72d4cb2a8e1f749dff97af99b071e – before 2e9e10657b04152ed0d6ecae8d0c02a3405e28f5f19d5870cbf72d4cb2a8e1f749dff97af99b071e – before 1437c95ab2a28b138d4521653583729f61ccb48bf19d5870cbf72d4cb2a8e1f749dff97af99b071e – before cb6039b68efa547b676a8a10fc4618d9d1865c23f19d5870cbf72d4cb2a8e1f749dff97af99b071e – before de985264eef64be8a90595908f2e6a87946dad34f19d5870cbf72d4cb2a8e1f749dff97af99b071e – before 1f5ccd22ff482639133f2a0fe08f6d19d0e68717f19d5870cbf72d4cb2a8e1f749dff97af99b071e – before 1d3ad183943b38eec2acf72a0ae98e635dc8456b
Linux Linux 3.8

References