# drm/amd: Fix NULL pointer dereference in device cleanup

CVE record · `CVE-2026-43369`

- **Identifiers:** `CVE-2026-43369`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 8 May 2026
- **Updated:** 6 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 8 May 2026, 14:21 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: `fc58ef30e0a1524ce72a8e873d773ba3b0830c7d to before 43025c941aced9a9009f9ff20eea4eb78c61deb8` (git)
  - affected: `6d7ac4a0ebb6b7bc885274aa8b2bd9971f07013c to before 767cd24d3c4ae847688877def4891943f6611ecd` (git)
  - affected: `39fc2bc4da0082c226cbee331f0a5d44db3997da to before 062ea905fff7756b2e87143ffccaece5cdb44267` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.18.16 to before 6.18.19` (semver)
  - affected: `6.19.6 to before 6.19.9` (semver)
  - Other versions: unaffected

## Machine-written summary

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

> The drm/amd GPU driver in the Linux kernel can dereference a NULL pointer during device cleanup after GPU initialization fails on an unsupported hardware block, which leads to a kernel NULL pointer dereference. Affected versions include 6.18.16 before 6.18.19 and 6.19.6 before 6.19.9. The source gives no details on what access an attacker would need. Upgrade to 6.18.19, 6.19.9, or a later fixed kernel.

Written 17 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.0012, the 1st percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 8 May 2026, 14:21 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-43369)
- 8 May 2026, 15:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-43369)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/43025c941aced9a9009f9ff20eea4eb78c61deb8>
- <https://git.kernel.org/stable/c/767cd24d3c4ae847688877def4891943f6611ecd>
- <https://git.kernel.org/stable/c/062ea905fff7756b2e87143ffccaece5cdb44267>

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

---

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