drm/i915/dsi: Don't do DSC horizontal timing adjustments in command mode
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.160, 6.12.81, 6.18.22, 6.19.12
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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)
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 53693f02d80e0a909e76c2a25f8aac8515f959db · fixed in 481f7a463ae4bea9503ae7fa1481ad75dc872af4; From 53693f02d80e0a909e76c2a25f8aac8515f959db · fixed in 55efe8402f46af8399c8b634a18b130a05fd7820; From 53693f02d80e0a909e76c2a25f8aac8515f959db · fixed in 86e926b108880c0109b8635e459450447156aeb7; From 53693f02d80e0a909e76c2a25f8aac8515f959db · fixed in 33b5336e4fd8ba0e40a12989cadb3f5534a0f9e4; From 53693f02d80e0a909e76c2a25f8aac8515f959db · fixed in 4dfce79e098915d8e5fc2b9e1d980bc3251dd32c
- Linux Linux
5.6
- KernelLinux
From 5.6.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.81; From 6.13.0 · fixed in 6.18.22; From 6.19.0 · fixed in 6.19.12