csirt@kutim:~/threat-intel/cve/CVE-2026-31448

Katalog CVE

CVSS 9.4 · Critical EPSS 0,65%

Kerentanan Loop with Unreachable Exit Condition ('Infinite Loop') pada linux kernel. Skor CVSS 3.1 9.4 (Critical) menurut CNA.

Deskripsi (NVD)

In the Linux kernel, the following vulnerability has been resolved: ext4: avoid infinite loops caused by residual data On the mkdir/mknod path, when mapping logical blocks to physical blocks, if inserting a new extent into the extent tree fails (in this example, because the file system disabled the huge file feature when marking the inode as dirty), ext4_ext_map_blocks() only calls ext4_free_blocks() to reclaim the physical block without deleting the corresponding data in the extent tree. This causes subsequent mkdir operations to reference the previously reclaimed physical block number again, even though this physical block is already being used by the xattr block. Therefore, a situation arises where both the directory and xattr are using the same buffer head block in memory simultaneously. The above causes ext4_xattr_block_set() to enter an infinite loop about "inserted" and cannot release the inode lock, ultimately leading to the 143s blocking problem mentioned in [1]. If the metadata is corrupted, then trying to remove some extent space can do even more harm. Also in case EXT4_GET_BLOCKS_DELALLOC_RESERVE was passed, remove space wrongly update quota information. Jan Kara suggests distinguishing between two cases: 1) The error is ENOSPC or EDQUOT - in this case the filesystem is fully consistent and we must maintain its consistency including all the accounting. However these errors can happen only early before we've inserted the extent into the extent tree. So current code works correctly for this case. 2) Some other error - this means metadata is corrupted. We should strive to do as few modifications as possible to limit damage. So I'd just skip freeing of allocated blocks. [1] INFO: task syz.0.17:5995 blocked for more than 143 seconds. Call Trace: inode_lock_nested include/linux/fs.h:1073 [inline] __start_dirop fs/namei.c:2923 [inline] start_dirop fs/namei.c:2934 [inline]

Rincian

Terbit di NVD
22 April 2026
Terakhir diubah
14 Juli 2026
Status NVD
Modified
CVSS 3.1
9.4 (Critical), sumber CNA
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H · uraikan di kalkulator
Jenis kelemahan (CWE)
CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop')
EPSS (30 hari)
0,65% peluang dieksploitasi; lebih tinggi dari 49,8% CVE lain

Produk dan versi terdampak

VendorProdukVersi terdampak
linux linux kernel Versi 2.6.22.1 hingga sebelum 6.1.168
linux linux kernel Versi 6.2 hingga sebelum 6.6.131
linux linux kernel Versi 6.7 hingga sebelum 6.12.80
linux linux kernel Versi 6.13 hingga sebelum 6.18.21
linux linux kernel Versi 6.19 hingga sebelum 6.19.11
linux linux kernel Versi 2.6.22
linux linux kernel Versi 2.6.22 rc4
linux linux kernel Versi 2.6.22 rc5
linux linux kernel Versi 2.6.22 rc6
linux linux kernel Versi 2.6.22 rc7
linux linux kernel Versi 7.0 rc1
linux linux kernel Versi 7.0 rc2
linux linux kernel Versi 7.0 rc3
linux linux kernel Versi 7.0 rc4
linux linux kernel Versi 7.0 rc5

> Data dari konfigurasi CPE di NVD.

Referensi dan perbaikan

Sumber: NVD · CVE.org · EPSS. Halaman ini disusun otomatis dari data tersebut; pembaruan terakhir 5 Okt 2026, 20:11 WITA. Kalau sistem di Perangkat Daerah memakai produk ini dan butuh bantuan, laporkan lewat kanal pelaporan.