# drm/amdgpu: fix pci device refcount leak

CVE record · `CVE-2022-50718`

- **Identifiers:** `CVE-2022-50718`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 24 Dec 2025
- **Updated:** 11 May 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 24 Dec 2025, 12:22 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: `3f12acc8d6d4b2e62fab8f652d7075a859d80b42 to before 3725a8f26bdbc38dfdf545836117f1e069277c91` (git)
  - affected: `3f12acc8d6d4b2e62fab8f652d7075a859d80b42 to before 02105f0b3021ee5853b2fa50853c42f35fc01cfd` (git)
  - affected: `3f12acc8d6d4b2e62fab8f652d7075a859d80b42 to before f13661b72a61708cecb06562f8acff068a4f31f7` (git)
  - affected: `3f12acc8d6d4b2e62fab8f652d7075a859d80b42 to before d7352b410471cbebf6350b2990bae82bb0d59a76` (git)
  - affected: `3f12acc8d6d4b2e62fab8f652d7075a859d80b42 to before b85e285e3d6352b02947fc1b72303673dfacb0aa` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.8`
  - unaffected: `before 5.8` (semver)
  - unaffected: `5.10.163 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.86 to 5.15.*, inclusive` (semver)
  - unaffected: `6.0.16 to 6.0.*, inclusive` (semver)
  - unaffected: `6.1.2 to 6.1.*, inclusive` (semver)
  - unaffected: `6.2 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.0024, the 14th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 24 Dec 2025, 13:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-50718)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/3725a8f26bdbc38dfdf545836117f1e069277c91>
- <https://git.kernel.org/stable/c/02105f0b3021ee5853b2fa50853c42f35fc01cfd>
- <https://git.kernel.org/stable/c/f13661b72a61708cecb06562f8acff068a4f31f7>
- <https://git.kernel.org/stable/c/d7352b410471cbebf6350b2990bae82bb0d59a76>
- <https://git.kernel.org/stable/c/b85e285e3d6352b02947fc1b72303673dfacb0aa>

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-50718>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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