drm/amd/display: Fix mismatched unlock for DMUB HW lock in HWSS fast path
Summary
| CVE | CVE-2026-43305 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-05-08 14:16:37 UTC |
| Updated | 2026-05-12 14:10:27 UTC |
| Description | 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. |
Risk And Classification
EPSS: 0.000180000 probability, percentile 0.050790000 (date 2026-05-12)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 7d041982fe11fff29b32a09228c4d52f159b56ad 4e387ad67efb100b645630ffbce7716786f52283 git | Not specified |
| CNA | Linux | Linux | affected 7d041982fe11fff29b32a09228c4d52f159b56ad af3303970da5ce5bfe6dffdd07f38f42aad603e0 git | Not specified |
| CNA | Linux | Linux | affected 6.19 | Not specified |
| CNA | Linux | Linux | unaffected 6.19 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.19.6 6.19.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.0 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/4e387ad67efb100b645630ffbce7716786f52283 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/af3303970da5ce5bfe6dffdd07f38f42aad603e0 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.