Answer in brief
CVE-2026-43305 records a Unknown severity vulnerability in drm/amd/display: Fix mismatched unlock for DMUB HW lock in HWSS fast path. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7d041982fe11fff29b32a09228c4d52f159b56ad <4e387ad67efb100b645630ffbce7716786f52283 || >=7d041982fe11fff29b32a09228c4d52f159b56ad <af3303970da5ce5bfe6dffdd07f38f42aad603e0 | 4e387ad67efb100b645630ffbce7716786f52283, af3303970da5ce5bfe6dffdd07f38f42aad603e0 |
| Linux/Linuxgeneric | 6.19 | Not reported |
Published upstream
May 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 6, 2026
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix mismatched unlock for DMUB HW lock in HWSS fast path [Why] The evaluation for whether we need to use the DMUB HW lock isn't the same as whether we need to unlock which results in a hang when the fast path is used for ASIC without FAMS support. [How] Store a flag that indicates whether we should use the lock and use that same flag to specify whether unlocking is needed.
Quoted source text, attributed separately from HOL analysis.