cveboard RSS feed

CVE-2022-49219

CVE.org · Published

Historical CVEsJSONAI instructions

Record status
Published
Identifier year (not publication year)
2022
Source publication
Source updated
Imported by cveboard
Source snapshot
cve_2026-10-24_midnight_baseline ·

Plain text

CNA source text (English)

vfio/pci: fix memory leak during D3hot to D0 transition

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.

Scoped product and version facts

Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.

Exploitation unknown; this catalogue does not assess exploitation.

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
unaffected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
51ef3a004b1eb6241e56b3aa8495769a092a4dc2affectedgitda426ad86027b849b877d4628b277ffbbd2f5325UnavailableNone listed
51ef3a004b1eb6241e56b3aa8495769a092a4dc2affectedgit4319f17fb8264ba39352b611dfa913a4d8c1d1a0UnavailableNone listed
51ef3a004b1eb6241e56b3aa8495769a092a4dc2affectedgit26ddd196e9eb264da8e1bdc4df8a94d62581c8b5UnavailableNone listed
51ef3a004b1eb6241e56b3aa8495769a092a4dc2affectedgitc8a1f8bd586ee31020614b8d48b702ece3e2ae44UnavailableNone listed
51ef3a004b1eb6241e56b3aa8495769a092a4dc2affectedgiteadf88ecf6ac7d6a9f47a76c6055d9a1987a8991UnavailableNone listed

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
affected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
5.1affectedUnavailableUnavailableUnavailableNone listed
0unaffectedsemver5.1UnavailableNone listed
5.10.237unaffectedsemverUnavailable5.10.*None listed
5.15.33unaffectedsemverUnavailable5.15.*None listed
5.16.19unaffectedsemverUnavailable5.16.*None listed
5.17.2unaffectedsemverUnavailable5.17.*None listed
5.18unaffectedoriginal_commit_for_fixUnavailable*None listed