CVE-2022-49219: vfio/pci: fix memory leak during D3hot to D0 transition

Q: What is the severity of CVE-2022-49219?

CVE-2022-49219 is categorized as a low severity vulnerability in the Linux kernel due to a memory leak during the D3hot to D0 transition.

Q: How do I fix CVE-2022-49219?

To fix CVE-2022-49219, upgrade to a patched version of the Linux kernel where this vulnerability has been addressed.

Q: What versions of the Linux kernel are affected by CVE-2022-49219?

CVE-2022-49219 affects Linux kernels from version 5.1 to 5.17.2, as well as 5.15.33 to 5.16.19.

Q: What component in the Linux kernel is affected by CVE-2022-49219?

CVE-2022-49219 specifically affects the vfio/pci component of the Linux kernel.

Q: What does CVE-2022-49219 impact?

CVE-2022-49219 impacts system stability by causing a memory leak when transitioning PCI devices from low power to active states.

Published Feb 26, 2025

Updated

In the Linux kernel, the following vulnerability has been resolved:

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

If 'vfiopcicoredevice::needspmrestore' is set (PCI device does not have NoSoftReset bit set in its PMCSR config register), then the current PCI state will be saved locally in 'vfiopcicoredevice::pmsave' during D0->D3hot transition and same will be restored back during D3hot->D0 transition. For saving the PCI state locally, pcistoresavedstate() is being used and the pciloadandfreesavedstate() 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 vfiopcisetpowerstate() for changing the power state to D0 explicitly. In this case, the memory pointed by 'pmsave' will never be freed. In a malicious sequence, the state changing to D3hot followed by VFIODEVICERESET/VFIODEVICEPCIHOTRESET can be run in a loop and it can cause an OOM situation.

This patch frees the earlier allocated memory first before overwriting 'pmsave' to prevent the mentioned memory leak.

Affected Software

133 affected componentsFixes available

Linux Linux kernel

Linux Linux kernel>=5.1<5.15.33

Linux Linux kernel>=5.16<5.16.19

Linux Linux kernel>=5.17<5.17.2

debian/linux<5.17.3-1

5.17.3-1

debian/linux<5.17.3-1

5.17.3-1

debian/linux<5.17.3-1

5.17.3-1

linux/kernel>=5.1.0<5.10.237

5.10.237

linux/kernel>=5.11.0<5.15.33

5.15.33

linux/kernel>=5.16.0<5.16.19

5.16.19

linux/kernel>=5.17.0<5.17.2

5.17.2

debian/linux

6.1.176-16.1.190-16.12.107-16.12.115-27.2.15-1

ubuntu/linux-hwe-edge*

ubuntu/linux-aws-5.0*

ubuntu/linux-aws-5.3*

ubuntu/linux-aws-5.4*

ubuntu/linux-azure*

ubuntu/linux-azure-5.3*

ubuntu/linux-azure-5.4*

ubuntu/linux-azure-edge*

ubuntu/linux-gcp*

ubuntu/linux-gcp-5.3*

ubuntu/linux-gcp-5.4*

ubuntu/linux-gke-4.15*

ubuntu/linux-gke-5.4*

ubuntu/linux-gkeop-5.4*

ubuntu/linux-hwe*

ubuntu/linux-hwe-5.4*

ubuntu/linux-hwe-edge*

ubuntu/linux-ibm-5.4*

ubuntu/linux-oem*

ubuntu/linux-oracle-5.0*

ubuntu/linux-oracle-5.3*

ubuntu/linux-oracle-5.4*

ubuntu/linux-raspi-5.4*

ubuntu/linux-azure-5.15<5.15.0-1008.9~20.04.1

5.15.0-1008.9~20.04.1

ubuntu/linux-hwe-5.15<5.15.0-41.44~20.04.1

5.15.0-41.44~20.04.1

ubuntu/linux-intel-iotg-5.15<5.15.0-1008.11~20.04.1

5.15.0-1008.11~20.04.1

ubuntu/linux-lowlatency-hwe-5.15<5.15.0-42.45~20.04.1

5.15.0-42.45~20.04.1

ubuntu/linux*

ubuntu/linux-aws*

ubuntu/linux-aws-5.11*

ubuntu/linux-aws-5.13*

ubuntu/linux-aws-5.8*

ubuntu/linux-azure*

ubuntu/linux-azure-5.11*

ubuntu/linux-azure-5.13*

ubuntu/linux-azure-5.8*

ubuntu/linux-azure-fde*

ubuntu/linux-bluefield*

ubuntu/linux-gcp*

ubuntu/linux-gcp-5.11*

ubuntu/linux-gcp-5.13*

ubuntu/linux-gcp-5.8*

ubuntu/linux-gke*

ubuntu/linux-gke-5.15*

ubuntu/linux-gkeop*

ubuntu/linux-gkeop-5.15*

ubuntu/linux-hwe-5.11*

ubuntu/linux-hwe-5.13*

ubuntu/linux-hwe-5.8*

ubuntu/linux-ibm*

ubuntu/linux-intel-5.13*

ubuntu/linux-iot*

ubuntu/linux-kvm*

ubuntu/linux-oem-5.10*

ubuntu/linux-oem-5.13*

ubuntu/linux-oem-5.6*

ubuntu/linux-oracle*

ubuntu/linux-oracle-5.11*

ubuntu/linux-oracle-5.13*

ubuntu/linux-oracle-5.8*

ubuntu/linux-raspi*

ubuntu/linux-raspi2*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.11*

ubuntu/linux-riscv-5.8*

ubuntu/linux-xilinx-zynqmp*

ubuntu/linux-aws-fips*

ubuntu/linux-azure-fips*

ubuntu/linux-fips*

ubuntu/linux-gcp-fips*

ubuntu/linux-aws-fips*

ubuntu/linux-azure-fips*

ubuntu/linux-fips*

ubuntu/linux-gcp-fips*

ubuntu/linux<5.15.0-37.39

5.15.0-37.39

ubuntu/linux-allwinner-5.19*

ubuntu/linux-aws<5.15.0-1011.14

5.15.0-1011.14

ubuntu/linux-aws-5.19*

ubuntu/linux-aws-6.2*

ubuntu/linux-aws-6.5*

ubuntu/linux-azure<5.15.0-1010.12

5.15.0-1010.12

ubuntu/linux-azure-5.19*

ubuntu/linux-azure-6.2*

ubuntu/linux-azure-6.5*

ubuntu/linux-azure-fde-5.19*

ubuntu/linux-azure-fde-6.2*

ubuntu/linux-gcp<5.15.0-1008.12

5.15.0-1008.12

ubuntu/linux-gcp-5.19*

ubuntu/linux-gcp-6.2*

ubuntu/linux-gcp-6.5*

ubuntu/linux-gke<5.15.0-1008.10

5.15.0-1008.10

ubuntu/linux-hwe-5.19*

ubuntu/linux-hwe-6.2*

ubuntu/linux-hwe-6.5*

ubuntu/linux-ibm<5.15.0-1007.8

5.15.0-1007.8

ubuntu/linux-intel-iot-realtime*

ubuntu/linux-intel-iotg<5.15.0-1008.11

5.15.0-1008.11

ubuntu/linux-kvm<5.15.0-1010.11

5.15.0-1010.11

ubuntu/linux-lowlatency<5.15.0-37.39

5.15.0-37.39

ubuntu/linux-lowlatency-hwe-5.19*

ubuntu/linux-lowlatency-hwe-6.2*

ubuntu/linux-lowlatency-hwe-6.5*

ubuntu/linux-nvidia-6.2*

ubuntu/linux-nvidia-6.5*

ubuntu/linux-oem-5.17*

ubuntu/linux-oem-6.0*

ubuntu/linux-oem-6.1*

ubuntu/linux-oem-6.5*

ubuntu/linux-oracle<5.15.0-1009.12

5.15.0-1009.12

ubuntu/linux-oracle-6.5*

ubuntu/linux-raspi<5.15.0-1011.13

5.15.0-1011.13

ubuntu/linux-realtime*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.19*

ubuntu/linux-riscv-6.5*

ubuntu/linux-starfive-5.19*

ubuntu/linux-starfive-6.2*

ubuntu/linux-starfive-6.5*

ubuntu/linux-realtime<5.15.0-1014.14

5.15.0-1014.14

ubuntu/linux-raspi-realtime*

ubuntu/linux-vmware*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade debian/linux to a version that resolves this vulnerability.
Fixed in 5.17.3-1
Upgrade
Upgrade ubuntu/linux-azure-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1008.9~20.04.1
Upgrade
Upgrade ubuntu/linux-hwe-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-41.44~20.04.1
Upgrade
Upgrade ubuntu/linux-intel-iotg-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1008.11~20.04.1
Upgrade
Upgrade ubuntu/linux-lowlatency-hwe-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-42.45~20.04.1
Upgrade
Upgrade ubuntu/linux to a version that resolves this vulnerability.
Fixed in 5.15.0-37.39
Upgrade
Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.
Fixed in 5.15.0-1011.14
Upgrade
Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.
Fixed in 5.15.0-1010.12
Upgrade
Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.
Fixed in 5.15.0-1008.12
Upgrade
Upgrade ubuntu/linux-gke to a version that resolves this vulnerability.
Fixed in 5.15.0-1008.10
Upgrade
Upgrade ubuntu/linux-ibm to a version that resolves this vulnerability.
Fixed in 5.15.0-1007.8
Upgrade
Upgrade ubuntu/linux-intel-iotg to a version that resolves this vulnerability.
Fixed in 5.15.0-1008.11
Upgrade
Upgrade ubuntu/linux-kvm to a version that resolves this vulnerability.
Fixed in 5.15.0-1010.11
Upgrade
Upgrade ubuntu/linux-lowlatency to a version that resolves this vulnerability.
Fixed in 5.15.0-37.39
Upgrade
Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.
Fixed in 5.15.0-1009.12
Upgrade
Upgrade ubuntu/linux-raspi to a version that resolves this vulnerability.
Fixed in 5.15.0-1011.13
Upgrade
Upgrade ubuntu/linux-realtime to a version that resolves this vulnerability.
Fixed in 5.15.0-1014.14
Upgrade
Upgrade linux/Kernel to a version that resolves this vulnerability.
Fixed in 5.10.237
Upgrade
Upgrade linux/Kernel to a version that resolves this vulnerability.
Fixed in 5.15.33
Upgrade
Upgrade linux/Kernel to a version that resolves this vulnerability.
Fixed in 5.16.19
Upgrade
Upgrade linux/Kernel to a version that resolves this vulnerability.
Fixed in 5.17.2
Upgrade
Upgrade debian/linux to a version that resolves this vulnerability.
Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.115-2Fixed in 7.2.15-1

Event History

Feb 26, 2025

CVE Published

via MITRE·01:55 AM

Data Sourced

via MITRE·01:55 AM

Description

Data Sourced

via OSV·01:55 AM

DescriptionAffected Software

Data Sourced

via NVD·07:00 AM

RemedyDescriptionSeverityWeaknessAffected Software

Nov 11, 2026

Data Sourced

via OSV·09:37 AM

Severity

Peer vulnerabilities

Found alongside the following vulnerabilities.

DLA-4178-1

Frequently Asked Questions

What is the severity of CVE-2022-49219?

CVE-2022-49219 is categorized as a low severity vulnerability in the Linux kernel due to a memory leak during the D3hot to D0 transition.

How do I fix CVE-2022-49219?

To fix CVE-2022-49219, upgrade to a patched version of the Linux kernel where this vulnerability has been addressed.

What versions of the Linux kernel are affected by CVE-2022-49219?

CVE-2022-49219 affects Linux kernels from version 5.1 to 5.17.2, as well as 5.15.33 to 5.16.19.

What component in the Linux kernel is affected by CVE-2022-49219?

CVE-2022-49219 specifically affects the vfio/pci component of the Linux kernel.

What does CVE-2022-49219 impact?

CVE-2022-49219 impacts system stability by causing a memory leak when transitioning PCI devices from low power to active states.

CVE-2022-49219: vfio/pci: fix memory leak during D3hot to D0 transition

Affected Software

Remediation

Event History

Peer vulnerabilities

Frequently Asked Questions

What is the severity of CVE-2022-49219?

How do I fix CVE-2022-49219?

What versions of the Linux kernel are affected by CVE-2022-49219?

What component in the Linux kernel is affected by CVE-2022-49219?

What does CVE-2022-49219 impact?

Company

Resources

Contact