CVE-2026-31767: Linux kernel · drm/i915/dsi: Don't do DSC horizontal timing adjustments in command mode
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in 481f7a463ae4bea9503ae7fa1481ad75dc872af4 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 17:30 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 481f7a463ae4bea9503ae7fa1481ad75dc872af4, 86e926b108880c0109b8635e459450447156aeb7, 55efe8402f46af8399c8b634a18b130a05fd7820 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 1 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
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)
References
- git.kernel.org/stable/c/481f7a463ae4bea9503ae7fa1481ad75dc872af4 (opens in a new tab)
- git.kernel.org/stable/c/55efe8402f46af8399c8b634a18b130a05fd7820 (opens in a new tab)
- git.kernel.org/stable/c/86e926b108880c0109b8635e459450447156aeb7 (opens in a new tab)
- git.kernel.org/stable/c/33b5336e4fd8ba0e40a12989cadb3f5534a0f9e4 (opens in a new tab)
- git.kernel.org/stable/c/4dfce79e098915d8e5fc2b9e1d980bc3251dd32c (opens in a new tab)