{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-40167 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-40167 is a high-severity denial of service vulnerability in Linux, published on 12 Nov 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-40167 and fix it if it is affected.\n\nWhat it is: CVE-2025-40167 is a high-severity denial of service vulnerability in Linux, published on 12 Nov 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-40167 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-40167/ (Markdown: https://insights.sbomify.com/CVE-2025-40167/index.md)","id":"CVE-2025-40167","markdown":"https://insights.sbomify.com/CVE-2025-40167/index.md","name":"CVE-2025-40167","record":{"aliases":["AZL-69992","BELL-CVE-2025-40167","DEBIAN-CVE-2025-40167","GHSA-x383-8hmc-j634","ROOT-OS-DEBIAN-11-CVE-2025-40167","ROOT-OS-DEBIAN-13-CVE-2025-40167","ROOT-OS-UBUNTU-2404-CVE-2025-40167","UBUNTU-CVE-2025-40167"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel ext4","requires_auth":"none","summary":"A corrupted ext4 filesystem with invalid flags causes a kernel BUG_ON, leading to denial of service when mounted without a journal.","user_interaction":"required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\next4: detect invalid INLINE_DATA + EXTENTS flag combination\n\nsyzbot reported a BUG_ON in ext4_es_cache_extent() when opening a verity\nfile on a corrupted ext4 filesystem mounted without a journal.\n\nThe issue is that the filesystem has an inode with both the INLINE_DATA\nand EXTENTS flags set:\n\n    EXT4-fs error (device loop0): ext4_cache_extents:545: inode #15:\n    comm syz.0.17: corrupted extent tree: lblk 0 \u003c prev 66\n\nInvestigation revealed that the inode has both flags set:\n    DEBUG: inode 15 - flag=1, i_inline_off=164, has_inline=1, extents_flag=1\n\nThis is an invalid combination since an inode should have either:\n- INLINE_DATA: data stored directly in the inode\n- EXTENTS: data stored in extent-mapped blocks\n\nHaving both flags causes ext4_has_inline_data() to return true, skipping\nextent tree validation in __ext4_iget(). The unvalidated out-of-order\nextents then trigger a BUG_ON in ext4_es_cache_extent() due to integer\nunderflow when calculating hole sizes.\n\nFix this by detecting this invalid flag combination early in ext4_iget()\nand rejecting the corrupted inode.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"ext4: detect invalid INLINE_DATA + EXTENTS flag combination","id":"CVE-2025-40167","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":8,"next":{"headline":"smc: Use __sk_dst_get() and dst_dev_rcu() in smc_clc_prfx_match().","id":"CVE-2025-40168"},"packages":[],"prev":{"headline":"drm/xe/guc: Check GuC running state before deregistering exec queue","id":"CVE-2025-40166"},"products":["Linux"],"published":"2025-11-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["Linux"]},"summary":"A corrupted ext4 filesystem with invalid flags causes a kernel BUG_ON, leading to denial of service when mounted without a journal.","url":"https://insights.sbomify.com/CVE-2025-40167/"}