Filesystem hang via stale ext4 extent mapping
Published Apr 22, 2026 · Updated Apr 22, 2026
Infinite loop in ext4 in Linux Kernel allows remote attackers to hang filesystem operations through directory-creation requests. ext4_ext_map_blocks() frees a physical block after a failed extent insertion but leaves its mapping in the extent tree, allowing later mkdir or mknod activity to reuse the stale block as an xattr block. The trigger requires a post-insertion metadata error; the resulting buffer-head alias can trap ext4_xattr_block_set() in a loop while the inode lock remains held.
Summary
What happened
Infinite loop in ext4 in Linux Kernel allows remote attackers to hang filesystem operations through directory-creation requests. ext4_ext_map_blocks() frees a physical block after a failed extent insertion but leaves its mapping in the extent tree, allowing later mkdir or mknod activity to reuse the stale block as an xattr block. The trigger requires a post-insertion metadata error; the resulting buffer-head alias can trap ext4_xattr_block_set() in a loop while the inode lock remains held.
The record
- CVE
- CVE-2026-31448
- Published
- Apr 22, 2026
- Updated
- Apr 22, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-835, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 22, 2026CVE publishedPublication date reported by the CVE source.
- Apr 22, 2026Record 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3a7667595bcad84da53fc156a418e110267c3412
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <416c86f30f91b4fb2642ef6b102596ca898f41a5
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5422fe71d26d42af6c454ca9527faaad4e677d6c
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <64f425b06b3bea9abc8977fd3982779b3ad070c9
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c66545e83a802c3851d9be27a41c0479dd29ff0c
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ecc50bfca9b5c2ee6aeef998181689b80477367b
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