Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-31767drm/i915/dsi: Don't do DSC horizontal timing adjustments in command mode

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)

Timeline

  1. ID reserved

    By Linux

  2. · 53 days later

    Published

  3. · 6 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-31767, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 53693f02d80e0a909e76c2a25f8aac8515f959db – < 80cc84bdc49addaee6b6e4f735f574ab5a424c42
    • affected 53693f02d80e0a909e76c2a25f8aac8515f959db – < 481f7a463ae4bea9503ae7fa1481ad75dc872af4
    • affected 53693f02d80e0a909e76c2a25f8aac8515f959db – < 55efe8402f46af8399c8b634a18b130a05fd7820
    • affected 53693f02d80e0a909e76c2a25f8aac8515f959db – < 86e926b108880c0109b8635e459450447156aeb7
    • affected 53693f02d80e0a909e76c2a25f8aac8515f959db – < 33b5336e4fd8ba0e40a12989cadb3f5534a0f9e4
    • affected 53693f02d80e0a909e76c2a25f8aac8515f959db – < 4dfce79e098915d8e5fc2b9e1d980bc3251dd32c
  • Linux · Linux

    • affected 5.6
    • unaffected < 5.6
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.81 – ≤ 6.12.*
    • unaffected 6.18.22 – ≤ 6.18.*
    • unaffected 6.19.12 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-31767 badge
[![CVE-2026-31767](https://cveledger.app/badge/CVE-2026-31767.svg)](https://cveledger.app/cve/CVE-2026-31767)

Record last updated .