CVE-2022-50286

Description

In the Linux kernel, the following vulnerability has been resolved: ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline When converting files with inline data to extents, delayed allocations made on a file system created with both the bigalloc and inline options can result in invalid extent status cache content, incorrect reserved cluster counts, kernel memory leaks, and potential kernel panics. With bigalloc, the code that determines whether a block must be delayed allocated searches the extent tree to see if that block maps to a previously allocated cluster. If not, the block is delayed allocated, and otherwise, it isn't. However, if the inline option is also used, and if the file containing the block is marked as able to store data inline, there isn't a valid extent tree associated with the file. The current code in ext4_clu_mapped() calls ext4_find_extent() to search the non-existent tree for a previously allocated cluster anyway, which typically finds nothing, as desired. However, a side effect of the search can be to cache invalid content from the non-existent tree (garbage) in the extent status tree, including bogus entries in the pending reservation tree. To fix this, avoid searching the extent tree when allocating blocks for bigalloc + inline files that are being converted from inline to extent mapped.

Gravité et risque d'exploitation

CVE-2022-50286 obtient un score CVSS de 7.8/10, soit une gravité élevée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.17 %, ce qui la place devant 5.7 % des CVE référencées.

Que faire ?

• Vérifiez si Linux (versions 4.19.271, <=6.1.*, <d440d6427a5e3a877c1c259b8d2b216ddb65e185, 4.20, 0, <9404839e0c9db5a517ea83c0ca3388b39d105fdf, <4.19.271, 4.19.270, <131294c35ed6f777bd4e79d42af13b5c41bf2775, <4.20, d40e09f701cf7a44e595a558b067b2b4f67fbf87, <=5.10.*, 5.15.87, <6f4200ec76a0d31200c308ec5a71c68df5417004, <=6.0.*, 5.4.229, <c0c8edbc8abbe8f16d80a1d794d1ba2c12b6f193, <=5.4.*, <=4.19.*, 0b02f4c0d6d9e2c611dfbdd4317193e9dca740e6, 6.1.4, 5.10.163, <=*, <f83391339d8493b9ff24167516aaa5a5e88d8f81, <81b915181c630ee1cffa052e52874fe4e1ba91ac, <=5.15.*, 6.0.18, 6.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/f83391339d8493b9ff24167516aaa5a5e88d8f81
• https://git.kernel.org/stable/c/6f4200ec76a0d31200c308ec5a71c68df5417004
• https://git.kernel.org/stable/c/9404839e0c9db5a517ea83c0ca3388b39d105fdf
• https://git.kernel.org/stable/c/d440d6427a5e3a877c1c259b8d2b216ddb65e185
• https://git.kernel.org/stable/c/c0c8edbc8abbe8f16d80a1d794d1ba2c12b6f193
• https://git.kernel.org/stable/c/81b915181c630ee1cffa052e52874fe4e1ba91ac
• https://git.kernel.org/stable/c/131294c35ed6f777bd4e79d42af13b5c41bf2775