drm/amd/display: Fix mismatched unlock for DMUB HW lock in HWSS fast path
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
A mismatched DMUB hardware-lock unlock in the AMD display HWSS fast path can cause a hang when that path is used on ASICs without FAMS support. The input does not describe an attacker, access requirements, or user interaction.
Anyone running a Linux kernel with AMD display support should check their kernel version; affected versions are not specified.