Heimdall Security Logo

CVE-2022-49219

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.3%
Linux•Linux•Versions : 5.15.33, <=5.17.*, 5.18, 0, 5.10.237, <c8a1f8bd586ee31020614b8d48b702ece3e2ae44, <=5.10.*, <da426ad86027b849b877d4628b277ffbbd2f5325, <5.1, 5.16.19, 5.1, <=5.16.*, <eadf88ecf6ac7d6a9f47a76c6055d9a1987a8991, <26ddd196e9eb264da8e1bdc4df8a94d62581c8b5, 5.17.2, <=*, <=5.15.*, 51ef3a004b1eb6241e56b3aa8495769a092a4dc2, <4319f17fb8264ba39352b611dfa913a4d8c1d1a0

Description

In the Linux kernel, the following vulnerability has been resolved: vfio/pci: fix memory leak during D3hot to D0 transition If 'vfio_pci_core_device::needs_pm_restore' is set (PCI device does not have No_Soft_Reset bit set in its PMCSR config register), then the current PCI state will be saved locally in 'vfio_pci_core_device::pm_save' during D0->D3hot transition and same will be restored back during D3hot->D0 transition. For saving the PCI state locally, pci_store_saved_state() is being used and the pci_load_and_free_saved_state() will free the allocated memory. But for reset related IOCTLs, vfio driver calls PCI reset-related API's which will internally change the PCI power state back to D0. So, when the guest resumes, then it will get the current state as D0 and it will skip the call to vfio_pci_set_power_state() for changing the power state to D0 explicitly. In this case, the memory pointed by 'pm_save' will never be freed. In a malicious sequence, the state changing to D3hot followed by VFIO_DEVICE_RESET/VFIO_DEVICE_PCI_HOT_RESET can be run in a loop and it can cause an OOM situation. This patch frees the earlier allocated memory first before overwriting 'pm_save' to prevent the mentioned memory leak.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions 5.15.33, <=5.17.*, 5.18, 0, 5.10.237, <c8a1f8bd586ee31020614b8d48b702ece3e2ae44, <=5.10.*, <da426ad86027b849b877d4628b277ffbbd2f5325, <5.1, 5.16.19, 5.1, <=5.16.*, <eadf88ecf6ac7d6a9f47a76c6055d9a1987a8991, <26ddd196e9eb264da8e1bdc4df8a94d62581c8b5, 5.17.2, <=*, <=5.15.*, 51ef3a004b1eb6241e56b3aa8495769a092a4dc2, <4319f17fb8264ba39352b611dfa913a4d8c1d1a0) 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