Heimdall Security Logo

CVE-2024-40974

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

CVSS 7.8 · Élevée
EPSS 0.3%
Linux•Linux•Versions : <=6.1.*, 5.4.279, 2.6.19, 6.10, <3ad0034910a57aa88ed9976b1431b7b8c84e0048, 0, <ff2e185cf73df480ec69675936c4ee75a445c3e4, <a8c988d752b3d98d5cc1e3929c519a55ef55426c, <8aa11aa001576bf3b00dcb8559564ad7a3113588, b9377ffc3a03cde558d76349a262a1adbb6d3112, <=5.10.*, <19c166ee42cf16d8b156a6cb4544122d9a65d3ca, <=6.6.*, 6.6.36, <=6.9.*, 6.9.7, <262e942ff5a839b9e4f3302a8987928b0c8b8a2d, 5.15.162, <=5.4.*, <2.6.19, <=4.19.*, 5.10.221, <aa6107dcc4ce9a3451f2d729204713783b657257, 6.1.96, <=*, <=5.15.*, 4.19.317, <acf2b80c31c37acab040baa3cf5f19fbd5140b18

Description

In the Linux kernel, the following vulnerability has been resolved: powerpc/pseries: Enforce hcall result buffer validity and size plpar_hcall(), plpar_hcall9(), and related functions expect callers to provide valid result buffers of certain minimum size. Currently this is communicated only through comments in the code and the compiler has no idea. For example, if I write a bug like this: long retbuf[PLPAR_HCALL_BUFSIZE]; // should be PLPAR_HCALL9_BUFSIZE plpar_hcall9(H_ALLOCATE_VAS_WINDOW, retbuf, ...); This compiles with no diagnostics emitted, but likely results in stack corruption at runtime when plpar_hcall9() stores results past the end of the array. (To be clear this is a contrived example and I have not found a real instance yet.) To make this class of error less likely, we can use explicitly-sized array parameters instead of pointers in the declarations for the hcall APIs. When compiled with -Warray-bounds[1], the code above now provokes a diagnostic like this: error: array argument is too small; is of size 32, callee requires at least 72 [-Werror,-Warray-bounds] 60 | plpar_hcall9(H_ALLOCATE_VAS_WINDOW, retbuf, | ^ ~~~~~~ [1] Enabled for LLVM builds but not GCC for now. See commit 0da6e5fd6c37 ("gcc: disable '-Warray-bounds' for gcc-13 too") and related changes.

Gravité et risque d'exploitation

CVE-2024-40974 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.30 %, ce qui la place devant 21.5 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, 5.4.279, 2.6.19, 6.10, <3ad0034910a57aa88ed9976b1431b7b8c84e0048, 0, <ff2e185cf73df480ec69675936c4ee75a445c3e4, <a8c988d752b3d98d5cc1e3929c519a55ef55426c, <8aa11aa001576bf3b00dcb8559564ad7a3113588, b9377ffc3a03cde558d76349a262a1adbb6d3112, <=5.10.*, <19c166ee42cf16d8b156a6cb4544122d9a65d3ca, <=6.6.*, 6.6.36, <=6.9.*, 6.9.7, <262e942ff5a839b9e4f3302a8987928b0c8b8a2d, 5.15.162, <=5.4.*, <2.6.19, <=4.19.*, 5.10.221, <aa6107dcc4ce9a3451f2d729204713783b657257, 6.1.96, <=*, <=5.15.*, 4.19.317, <acf2b80c31c37acab040baa3cf5f19fbd5140b18) 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

Rechercher une autre CVE