drm/ast: Fix soft lockup
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/ast: Fix soft lockup
There is a while-loop in ast_dp_set_on_off() that could lead to infinite-loop. This is because the register, VGACRI-Dx, checked in this API is a scratch register actually controlled by a MCU, named DPMCU, in BMC.
These scratch registers are protected by scu-lock. If suc-lock is not off, DPMCU can not update these registers and then host will have soft lockup due to never updated status.
DPMCU is used to control DP and relative registers to handshake with host's VGA driver. Even the most time-consuming task, DP's link training, is less than 100ms. 200ms should be enough.
From the CVE record · Linux
A loop in the Linux kernel’s drm/ast ast_dp_set_on_off() function can run indefinitely if the BMC’s DPMCU cannot update a protected status register. This can cause a host soft lockup when scu-lock prevents the register update. The input does not specify how an attacker could trigger the condition or whether access or user interaction is required.
Engineers running Linux systems that use the drm/ast driver should check their kernel versions; affected versions were not provided.