CVE-2024-42145

Vulnérabilité élevée dans Linux (Linux)

CVSS 7.5 · Élevée
EPSS 0.9%
Linux•Linux•Versions : <=6.1.*, 2.6.12, 6.10, 0, <2.6.12, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, <62349fbf86b5e13b02721bdadf98c29afd1e7b5f, <a6627fba793cc75b7365d9504a0095fb2902dda4, 4.19.318, <=5.10.*, <=6.6.*, <b8c5f635997f49c625178d1a0cb32a80ed33abe6, <1288cf1cceb0e6df276e182f5412370fb4169bcb, <=6.9.*, <b4913702419d064ec4c4bbf7270643c95cc89a1b, 5.10.222, <=5.4.*, <63d202d948bb6d3a28cd8e8b96b160fa53e18baa, <ca0b44e20a6f3032224599f02e7c8fb49525c894, 6.9.9, <=4.19.*, <d73cb8862e4d6760ccc94d3b57b9ef6271400607, <=*, <=5.15.*, 5.4.280, 5.15.163, 6.1.98, 6.6.39

Description

In the Linux kernel, the following vulnerability has been resolved: IB/core: Implement a limit on UMAD receive List The existing behavior of ib_umad, which maintains received MAD packets in an unbounded list, poses a risk of uncontrolled growth. As user-space applications extract packets from this list, the rate of extraction may not match the rate of incoming packets, leading to potential list overflow. To address this, we introduce a limit to the size of the list. After considering typical scenarios, such as OpenSM processing, which can handle approximately 100k packets per second, and the 1-second retry timeout for most packets, we set the list size limit to 200k. Packets received beyond this limit are dropped, assuming they are likely timed out by the time they are handled by user-space. Notably, packets queued on the receive list due to reasons like timed-out sends are preserved even when the list is full.

Gravité et risque d'exploitation

CVE-2024-42145 obtient un score CVSS de 7.5/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.87 %, ce qui la place devant 58.1 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, 2.6.12, 6.10, 0, <2.6.12, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, <62349fbf86b5e13b02721bdadf98c29afd1e7b5f, <a6627fba793cc75b7365d9504a0095fb2902dda4, 4.19.318, <=5.10.*, <=6.6.*, <b8c5f635997f49c625178d1a0cb32a80ed33abe6, <1288cf1cceb0e6df276e182f5412370fb4169bcb, <=6.9.*, <b4913702419d064ec4c4bbf7270643c95cc89a1b, 5.10.222, <=5.4.*, <63d202d948bb6d3a28cd8e8b96b160fa53e18baa, <ca0b44e20a6f3032224599f02e7c8fb49525c894, 6.9.9, <=4.19.*, <d73cb8862e4d6760ccc94d3b57b9ef6271400607, <=*, <=5.15.*, 5.4.280, 5.15.163, 6.1.98, 6.6.39) 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