CVE-2022-49530

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

CVSS 7.8 · Élevée
EPSS 0.3%
Linux•Linux•Versions : <=5.17.*, 5.15.46, <43eb9b667b95f2a31c63e8949b0d2161b9be59c3, 0, 5.19, <=4.9.*, 5.18.3, <=5.10.*, <=4.14.*, 5.10.121, <6c5bdaa1325be7f04b79ea992ab216739192d342, 5.17.14, 4.19.247, 5.4.198, <=5.18.*, <=5.4.*, <c0e811c4ccf3b42705976285e3a94cc82dea7300, 841686df9f7d2942cfd94d024b8591fa3f74ef7c, <f3fa2becf2fc25b6ac7cf8d8b1a2e4a86b3b72bd, <4.9, 4.14.283, <=4.19.*, <ca1ce206894dd976275c78ee38dbc19873f22de9, <a5ce7051db044290b1a95045ff03c249005a3aa4, <fd2eff8b9dcbe469c3b7bbbc7083ab5ed94de07b, <=*, <af832028af6f44c6c45645757079c4ed6884ade5, 4.9, <=5.15.*, <2615464854505188f909d0c07c37a6623693b5c7, 4.9.318

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amd/pm: fix double free in si_parse_power_table() In function si_parse_power_table(), array adev->pm.dpm.ps and its member is allocated. If the allocation of each member fails, the array itself is freed and returned with an error code. However, the array is later freed again in si_dpm_fini() function which is called when the function returns an error. This leads to potential double free of the array adev->pm.dpm.ps, as well as leak of its array members, since the members are not freed in the allocation function and the array is not nulled when freed. In addition adev->pm.dpm.num_ps, which keeps track of the allocated array member, is not updated until the member allocation is successfully finished, this could also lead to either use after free, or uninitialized variable access in si_dpm_fini(). Fix this by postponing the free of the array until si_dpm_fini() and increment adev->pm.dpm.num_ps everytime the array member is allocated.

Gravité et risque d'exploitation

CVE-2022-49530 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.28 %, ce qui la place devant 19.6 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=5.17.*, 5.15.46, <43eb9b667b95f2a31c63e8949b0d2161b9be59c3, 0, 5.19, <=4.9.*, 5.18.3, <=5.10.*, <=4.14.*, 5.10.121, <6c5bdaa1325be7f04b79ea992ab216739192d342, 5.17.14, 4.19.247, 5.4.198, <=5.18.*, <=5.4.*, <c0e811c4ccf3b42705976285e3a94cc82dea7300, 841686df9f7d2942cfd94d024b8591fa3f74ef7c, <f3fa2becf2fc25b6ac7cf8d8b1a2e4a86b3b72bd, <4.9, 4.14.283, <=4.19.*, <ca1ce206894dd976275c78ee38dbc19873f22de9, <a5ce7051db044290b1a95045ff03c249005a3aa4, <fd2eff8b9dcbe469c3b7bbbc7083ab5ed94de07b, <=*, <af832028af6f44c6c45645757079c4ed6884ade5, 4.9, <=5.15.*, <2615464854505188f909d0c07c37a6623693b5c7, 4.9.318) 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