# drm/amd/display: Fix mismatched unlock for DMUB HW lock in HWSS fast path

CVE record · `CVE-2026-43305`

- **Identifiers:** `CVE-2026-43305`
- **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, 13:11 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: `7d041982fe11fff29b32a09228c4d52f159b56ad to before 4e387ad67efb100b645630ffbce7716786f52283` (git)
  - affected: `7d041982fe11fff29b32a09228c4d52f159b56ad to before af3303970da5ce5bfe6dffdd07f38f42aad603e0` (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 display driver (drm/amd/display) is affected in 6.19 before the fix. Versions before 6.19, 6.19.6 and later in the 6.19 series, and 7.0 and later are listed as unaffected. A mismatched unlock of the DMUB hardware lock in the HWSS fast path causes a hang on AMD hardware without FAMS support. The source gives few details on what access an attacker would need. Upgrade to 6.19.6 or later in the 6.19 series, or to 7.0 or later.

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

## Timeline

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

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/4e387ad67efb100b645630ffbce7716786f52283>
- <https://git.kernel.org/stable/c/af3303970da5ce5bfe6dffdd07f38f42aad603e0>

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

---

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