# drm/amd: fix potential memory leak

CVE record · `CVE-2022-50479`

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

Published by the CVE Program (CNA: Linux) at 4 Oct 2025, 15:16 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: `3cffeffe051a961417bc26f2053bced4cff83119 to before a6e6ab9caeac96b277a3fe7da1dfa8f69a591759` (git)
  - affected: `3cffeffe051a961417bc26f2053bced4cff83119 to before 6160216fd2c97107e8a9ab39863b056d677fcd85` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.0`
  - unaffected: `before 6.0` (semver)
  - unaffected: `6.0.3 to 6.0.*, inclusive` (semver)
  - unaffected: `6.1 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel's drm/amd graphics driver code is affected in version 6.0 before 6.0.3. It can leak a clock source object when a function returns NULL. The source gives few details on who can trigger it or what the impact is. Upgrade to Linux kernel 6.0.3 or later, or to 6.1 or later.

Written 16 Nov 2026.

## 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.0014, the 3rd percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 4 Oct 2025, 15:16 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2022-50479)
- 4 Oct 2025, 16:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-50479)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/a6e6ab9caeac96b277a3fe7da1dfa8f69a591759>
- <https://git.kernel.org/stable/c/6160216fd2c97107e8a9ab39863b056d677fcd85>

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

---

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