Linux kernel ext4 infinite loop from residual extent data
CVE-2026-31448Critical
When the ext4 filesystem fails to insert a new extent into the extent tree during mkdir or mknod operations, it frees the physical block but leaves the extent tree entry intact. This causes subsequent operations to reuse the freed physical block number, resulting in both a directory and extended attributes using the same block simultaneously. This leads to ext4_xattr_block_set() entering an infinite loop and blocking inode operations for extended periods. An attacker with filesystem access could trigger this by disabling the huge file feature on a filesystem with pending inode modifications.
Plain English summary of the NVD and CISA text, checked by machine against both.
Scores and dates
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H
Detail
Affected versions
- linux linux kernel: from 2.6.22.1, before 6.1.168
- linux linux kernel: from 6.2, before 6.6.131
- linux linux kernel: from 6.7, before 6.12.80
- linux linux kernel: from 6.13, before 6.18.21
- linux linux kernel: from 6.19, before 6.19.11
- linux linux kernel: 2.6.22
- linux linux kernel: 7.0
Reports naming this CVE1 in total
· All CISA Advisories
Siemens SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP (opens in a new tab)