CVE-2026-72159

Description

In the Linux kernel, the following vulnerability has been resolved: ocfs2: reject non-inline dinodes with i_size and zero i_clusters On a volume mounted without OCFS2_FEATURE_INCOMPAT_SPARSE_ALLOC, a non-inline regular file with non-zero i_size and zero i_clusters is structurally malformed: the extent map declares no allocated clusters yet the size header claims content exists. Keep rejecting that shape, but express it through a shared predicate so the same invariant is available to normal inode reads and online filecheck. The same zero-cluster shape is also malformed for non-inline directories. ocfs2 directory growth allocates backing storage before advancing i_size, and ocfs2_dir_foreach_blk_el() later walks until ctx->pos reaches i_size_read(inode). A forged directory dinode with a huge i_size and no clusters would repeatedly fail on holes while advancing through the claimed size. Sparse regular files remain exempt: on sparse-alloc volumes, truncate can legitimately grow i_size without allocating clusters. System inodes and inline-data dinodes also retain their separate storage rules. Mirror the check in ocfs2_filecheck_validate_inode_block() as well. filecheck reports through its own error namespace, so malformed size/cluster state is logged as a filecheck invalid-inode result rather than via ocfs2_error(), but it must not proceed into ocfs2_populate_inode().

Gravité et risque d'exploitation

CVE-2026-72159 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.22 %, ce qui la place devant 11.7 % des CVE référencées.

Que faire ?

• Vérifiez si Linux (versions <=6.1.*, <2.6.29, 6.18.40, <=6.12.*, 7.1.5, 0, <=7.1.*, <7ebc672fab7a76e1e47e0f2fc1ee48118d27fde4, 2.6.29, <38c1ef7ce50eb4af0f89038b8aba12396ddb9233, 6.1.178, <=5.10.*, <=6.6.*, 6.12.97, <416d3e5f8a30ed04fe21ba7dc73c2841c3b56265, <d837068eefbc2651fe5789bf75a0f945710f7b8e, <=6.18.*, 5.15.212, <83f6756a7b71adec0a41ae68e079a38906d59c6c, 6.6.145, 5.10.261, <ed0f938f946f16b772e99cb8c277ab57828e5be4, <3bfeb436d4be6a2beb56cab344770e93e6b07260, <=*, b657c95c11088d77fc1bfc9c84d940f778bf9d12, <=5.15.*, <2174c68f623b74bd8690a4a6a4a52882d8ac3dc3, 7.2) est présent sur votre parc.
• Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
• À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
• Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

• https://git.kernel.org/stable/c/416d3e5f8a30ed04fe21ba7dc73c2841c3b56265
• https://git.kernel.org/stable/c/ed0f938f946f16b772e99cb8c277ab57828e5be4
• https://git.kernel.org/stable/c/83f6756a7b71adec0a41ae68e079a38906d59c6c
• https://git.kernel.org/stable/c/38c1ef7ce50eb4af0f89038b8aba12396ddb9233
• https://git.kernel.org/stable/c/d837068eefbc2651fe5789bf75a0f945710f7b8e
• https://git.kernel.org/stable/c/2174c68f623b74bd8690a4a6a4a52882d8ac3dc3
• https://git.kernel.org/stable/c/3bfeb436d4be6a2beb56cab344770e93e6b07260
• https://git.kernel.org/stable/c/7ebc672fab7a76e1e47e0f2fc1ee48118d27fde4