drm/i915/dsi: Don't do DSC horizontal timing adjustments in command mode
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 53693f02d80e0a909e76c2a25f8aac8515f959db · < 4dfce79e098915d8e5fc2b9e1d980bc3251dd32c| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/i915/dsi: Don't do DSC horizontal timing adjustments in command mode
Stop adjusting the horizontal timing values based on the compression ratio in command mode. Bspec seems to be telling us to do this only in video mode, and this is also how the Windows driver does things.
This should also fix a div-by-zero on some machines because the adjusted htotal ends up being so small that we end up with line_time_us==0 when trying to determine the vtotal value in command mode.
Note that this doesn't actually make the display on the Huawei Matebook E work, but at least the kernel no longer explodes when the driver loads.
(cherry picked from commit 0b475e91ecc2313207196c6d7fd5c53e1a878525)
From the CVE record · Linux
The Linux kernel’s drm/i915/dsi driver can hit a divide-by-zero while calculating display timing in command mode. The issue can occur when the driver loads on some machines; the input does not describe an attacker, access requirements, or user interaction.
Engineers running Linux kernels with the drm/i915/dsi driver should check whether their kernel includes the fix; affected versions are not specified.