CVE-2022-49219

Advisory lineage Upstream: 0 Downstream: 5
Modified
Published: 26 Feb 2025, 01:55
Last modified:11 May 2026, 18:55

Vulnerability Summary

Overall Risk (default)
low
22/100
CVSS Score
5.5 MEDIUM
v3.1 (nvd)
EPSS Score
0.06% LOW
0% probability +0.02%
KEV
Not listed
Ransomware
No reports
Public exploits
None found
Dark Web
Not detected

Timeline

26 Feb 2025, 01:55
Published
Vulnerability first disclosed
11 May 2026, 18:55
Last Modified
Vulnerability information updated

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.

CVSS Metrics

  • v3.1•MEDIUM•Score: 5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

EPSS Trends

Current EPSS score: 0.06%• Percentile: 19%

Techniques & Countermeasures

  • CWE-401•Missing Release of Memory after Effective Lifetime

    The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

Affected Systems

  • linux•linux

    ≥ 51ef3a004b1eb6241e56b3aa8495769a092a4dc2, < da426ad86027b849b877d4628b277ffbbd2f5325 | ≥ 51ef3a004b1eb6241e56b3aa8495769a092a4dc2, < 4319f17fb8264ba39352b611dfa913a4d8c1d1a0 | ≥ 51ef3a004b1eb6241e56b3aa8495769a092a4dc2, < 26ddd196e9eb264da8e1bdc4df8a94d62581c8b5 | ≥ 51ef3a004b1eb6241e56b3aa8495769a092a4dc2, < c8a1f8bd586ee31020614b8d48b702ece3e2ae44 | ≥ 51ef3a004b1eb6241e56b3aa8495769a092a4dc2, < eadf88ecf6ac7d6a9f47a76c6055d9a1987a8991 | 5.1

  • linux•linux_kernel

    ≥ 5.1, < 5.15.33 | ≥ 5.16, < 5.16.19 | ≥ 5.17, < 5.17.2

References (6)