CVE-2026-31767

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-01. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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)

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

May 1, 2026

Last Modified

May 11, 2026

Advisory Details (4)

Auto-updated Aug 2, 2026
No patch confirmed yet.
generic

drm/i915/dsi: Don't do DSC horizontal timing adjustments in command mode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/86e926b108880c0109b8635e459450447156aeb7
generic

drm/i915/dsi: Don't do DSC horizontal timing adjustments in command mode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/55efe8402f46af8399c8b634a18b130a05fd7820
generic

drm/i915/dsi: Don't do DSC horizontal timing adjustments in command mode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4dfce79e098915d8e5fc2b9e1d980bc3251dd32c
generic

drm/i915/dsi: Don't do DSC horizontal timing adjustments in command mode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/33b5336e4fd8ba0e40a12989cadb3f5534a0f9e4

Vendor Advisories for CVE-2026-31767(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.12.81osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc5-1~exp1 (335 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (122 versions)6.19.12-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(13)

Data Freshness Timeline

(refreshed 7× in last 7d / 65× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 194 total refreshes for this CVE.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-24 14:17 UTCEPSS rescore
  3. 2026-08-23 00:19 UTCEPSS rescore
  4. 2026-08-21 23:49 UTCEPSS rescore
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-20 22:55 UTCEPSS rescore
  7. 2026-08-19 17:03 UTCEPSS rescore
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-17 13:43 UTCEG score recompute
  11. 2026-08-17 13:43 UTCVendor advisory
  12. 2026-08-17 13:43 UTCGHSA enrichment
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-16 05:17 UTCEG score recompute
  15. 2026-08-16 05:17 UTCVendor advisory
  16. 2026-08-16 05:17 UTCGHSA enrichment
  17. 2026-08-16 02:14 UTCEPSS rescore
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-14 03:46 UTCEG score recompute
  20. 2026-08-14 03:46 UTCVendor advisory
  21. 2026-08-14 03:46 UTCGHSA enrichment
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-13 00:48 UTCEG score recompute
  24. 2026-08-13 00:48 UTCVendor advisory
  25. 2026-08-13 00:48 UTCGHSA enrichment
Show 75 more
  1. 2026-08-12 13:50 UTCEPSS rescore
  2. 2026-08-12 01:19 UTCEG score recompute
  3. 2026-08-12 01:19 UTCVendor advisory
  4. 2026-08-12 01:19 UTCGHSA enrichment
  5. 2026-08-11 01:50 UTCEG score recompute
  6. 2026-08-11 01:50 UTCVendor advisory
  7. 2026-08-11 01:50 UTCGHSA enrichment
  8. 2026-08-11 00:00 UTCEPSS rescore
  9. 2026-08-10 02:22 UTCEG score recompute
  10. 2026-08-10 02:22 UTCVendor advisory
  11. 2026-08-10 02:22 UTCGHSA enrichment
  12. 2026-08-09 13:46 UTCEPSS rescore
  13. 2026-08-09 02:53 UTCEG score recompute
  14. 2026-08-09 02:53 UTCVendor advisory
  15. 2026-08-09 02:53 UTCGHSA enrichment
  16. 2026-08-08 16:37 UTCEPSS rescore
  17. 2026-08-08 02:01 UTCEG score recompute
  18. 2026-08-08 02:01 UTCVendor advisory
  19. 2026-08-08 02:01 UTCGHSA enrichment
  20. 2026-08-07 02:32 UTCEG score recompute
  21. 2026-08-07 02:32 UTCVendor advisory
  22. 2026-08-07 02:32 UTCGHSA enrichment
  23. 2026-08-06 13:46 UTCEPSS rescore
  24. 2026-08-05 22:35 UTCEG score recompute
  25. 2026-08-05 22:35 UTCVendor advisory
  26. 2026-08-05 22:35 UTCGHSA enrichment
  27. 2026-08-05 19:17 UTCEPSS rescore
  28. 2026-08-04 15:10 UTCEPSS rescore
  29. 2026-08-04 10:38 UTCEPSS rescore
  30. 2026-08-03 20:22 UTCEG score recompute
  31. 2026-08-03 20:22 UTCVendor advisory
  32. 2026-08-03 20:22 UTCGHSA enrichment
  33. 2026-08-03 10:36 UTCEPSS rescore
  34. 2026-08-02 05:39 UTCEG score recompute
  35. 2026-08-02 05:39 UTCVendor advisory
  36. 2026-08-02 05:39 UTCGHSA enrichment
  37. 2026-08-02 02:27 UTCEPSS rescore
  38. 2026-07-30 16:28 UTCEPSS rescore
  39. 2026-07-30 01:30 UTCEPSS rescore
  40. 2026-07-28 15:36 UTCEPSS rescore
  41. 2026-07-26 14:54 UTCEPSS rescore
  42. 2026-07-26 14:54 UTCEPSS rescore
  43. 2026-07-25 14:18 UTCEPSS rescore
  44. 2026-07-25 14:17 UTCEPSS rescore
  45. 2026-07-24 14:17 UTCEPSS rescore
  46. 2026-07-23 14:18 UTCEPSS rescore
  47. 2026-07-23 14:18 UTCEPSS rescore
  48. 2026-07-23 03:08 UTCEG score recompute
  49. 2026-07-22 14:08 UTCEPSS rescore
  50. 2026-07-22 14:08 UTCEPSS rescore
  51. 2026-07-21 15:24 UTCEPSS rescore
  52. 2026-07-21 15:24 UTCEPSS rescore
  53. 2026-07-20 17:08 UTCEPSS rescore
  54. 2026-07-20 17:08 UTCEPSS rescore
  55. 2026-07-19 19:48 UTCOSV refresh
  56. 2026-07-19 14:31 UTCEPSS rescore
  57. 2026-07-19 14:31 UTCEPSS rescore
  58. 2026-07-19 02:29 UTCEPSS rescore
  59. 2026-07-18 10:04 UTCEPSS rescore
  60. 2026-07-18 10:04 UTCEPSS rescore
  61. 2026-07-16 17:03 UTCEPSS rescore
  62. 2026-07-16 17:03 UTCEPSS rescore
  63. 2026-07-15 02:00 UTCEPSS rescore
  64. 2026-07-15 02:00 UTCEPSS rescore
  65. 2026-07-13 22:30 UTCEPSS rescore
  66. 2026-07-13 06:13 UTCEPSS rescore
  67. 2026-07-13 06:13 UTCEPSS rescore
  68. 2026-07-12 05:46 UTCEPSS rescore
  69. 2026-07-11 08:27 UTCEPSS rescore
  70. 2026-07-09 19:10 UTCEPSS rescore
  71. 2026-07-08 15:15 UTCEPSS rescore
  72. 2026-07-07 13:46 UTCEPSS rescore
  73. 2026-07-06 16:27 UTCEPSS rescore
  74. 2026-07-06 16:27 UTCEPSS rescore
  75. 2026-07-06 02:23 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-31767?
CVE-2026-31767 is a medium vulnerability published on May 1, 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…
When was CVE-2026-31767 disclosed?
CVE-2026-31767 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on May 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31767 actively exploited?
CVE-2026-31767 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.8% of all scored CVEs.
What is the CVSS score of CVE-2026-31767?
CVE-2026-31767 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-31767?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31767, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31767

Explore →

Is Your Infrastructure Affected by CVE-2026-31767?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.