# drm/amd/pm: Fix null pointer dereference issue

CVE record · `CVE-2026-43131`

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

Published by the CVE Program (CNA: Linux) at 6 May 2026, 11:27 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: `80e462c5b1963059dd78ee4650a3dfd53de4a10f to before 8e035505fa0e5b7c4306fd3f4e27f8e8f5bfad8c` (git)
  - affected: `80e462c5b1963059dd78ee4650a3dfd53de4a10f to before 1197366cca89a4c44c541ddedb8ce8bf0757993d` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.19`
  - unaffected: `before 6.19` (semver)
  - unaffected: `6.19.6 to 6.19.*, inclusive` (semver)
  - unaffected: `7.0 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 AMD power management code (drm/amd/pm) is affected in version 6.19. The source gives few details: a null pointer dereference occurs during RAS initialization when the SMU is disabled, and it does not say what an attacker needs. Upgrade to Linux 6.19.6 or 7.0 or later; no workaround is listed.

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

## Timeline

- 6 May 2026, 11:27 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-43131)
- 6 May 2026, 12:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-43131)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/8e035505fa0e5b7c4306fd3f4e27f8e8f5bfad8c>
- <https://git.kernel.org/stable/c/1197366cca89a4c44c541ddedb8ce8bf0757993d>

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

---

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