Answer in brief
CVE-2026-31767 records a Unknown severity vulnerability in drm/i915/dsi: Don't do DSC horizontal timing adjustments in command mode. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=53693f02d80e0a909e76c2a25f8aac8515f959db <481f7a463ae4bea9503ae7fa1481ad75dc872af4 || >=53693f02d80e0a909e76c2a25f8aac8515f959db <55efe8402f46af8399c8b634a18b130a05fd7820 || >=53693f02d80e0a909e76c2a25f8aac8515f959db <86e926b108880c0109b8635e459450447156aeb7 || >=53693f02d80e0a909e76c2a25f8aac8515f959db <33b5336e4fd8ba0e40a12989cadb3f5534a0f9e4 || >=53693f02d80e0a909e76c2a25f8aac8515f959db <4dfce79e098915d8e5fc2b9e1d980bc3251dd32c | 481f7a463ae4bea9503ae7fa1481ad75dc872af4, 55efe8402f46af8399c8b634a18b130a05fd7820, 86e926b108880c0109b8635e459450447156aeb7, 33b5336e4fd8ba0e40a12989cadb3f5534a0f9e4, 4dfce79e098915d8e5fc2b9e1d980bc3251dd32c |
| Linux/Linuxgeneric | 5.6 | Not reported |
Published upstream
May 1, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 21, 2026
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)
Quoted source text, attributed separately from HOL analysis.