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

CVE record · `CVE-2022-49219`

- **Identifiers:** `CVE-2022-49219`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 26 Feb 2025
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 26 Feb 2025, 01:55 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `51ef3a004b1eb6241e56b3aa8495769a092a4dc2 to before da426ad86027b849b877d4628b277ffbbd2f5325` (git)
  - affected: `51ef3a004b1eb6241e56b3aa8495769a092a4dc2 to before 4319f17fb8264ba39352b611dfa913a4d8c1d1a0` (git)
  - affected: `51ef3a004b1eb6241e56b3aa8495769a092a4dc2 to before 26ddd196e9eb264da8e1bdc4df8a94d62581c8b5` (git)
  - affected: `51ef3a004b1eb6241e56b3aa8495769a092a4dc2 to before c8a1f8bd586ee31020614b8d48b702ece3e2ae44` (git)
  - affected: `51ef3a004b1eb6241e56b3aa8495769a092a4dc2 to before eadf88ecf6ac7d6a9f47a76c6055d9a1987a8991` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.1`
  - unaffected: `before 5.1` (semver)
  - unaffected: `5.10.237 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.33 to 5.15.*, inclusive` (semver)
  - unaffected: `5.16.19 to 5.16.*, inclusive` (semver)
  - unaffected: `5.17.2 to 5.17.*, inclusive` (semver)
  - unaffected: `5.18 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0027, the 19th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 26 Feb 2025, 01:55 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2022-49219)
- 26 Feb 2025, 07:00 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-49219)

## Sources

- [CVE List: CVE-2022-49219](https://www.cve.org/CVERecord?id=CVE-2022-49219)
- [NVD: CVE-2022-49219](https://nvd.nist.gov/vuln/detail/CVE-2022-49219)

### References from the CNA

- <https://git.kernel.org/stable/c/da426ad86027b849b877d4628b277ffbbd2f5325>
- <https://git.kernel.org/stable/c/4319f17fb8264ba39352b611dfa913a4d8c1d1a0>
- <https://git.kernel.org/stable/c/26ddd196e9eb264da8e1bdc4df8a94d62581c8b5>
- <https://git.kernel.org/stable/c/c8a1f8bd586ee31020614b8d48b702ece3e2ae44>
- <https://git.kernel.org/stable/c/eadf88ecf6ac7d6a9f47a76c6055d9a1987a8991>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2022-49219>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2022-49219/>. Everything for agents: <https://agentprime.io/llms.txt>.
