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-68254drm/i915/vrr: require valid min/max vfreq for VRR

Description

In the Linux kernel, the following vulnerability has been resolved: drm/i915/vrr: require valid min/max vfreq for VRR Ensure the EDID provided min/max vfreq are valid. Most scenarios are already covered (by coincidence) through the checks in intel_vrr_is_capable() and intel_vrr_is_in_range(), but be more explicit about it. At worst, a zero min_vfreq could lead to a division by zero in intel_vrr_compute_vmax(). Discovered using AI-assisted static analysis confirmed by Intel Product Security. (cherry picked from commit 1765cf59f517b02f3b0591fe5120930d08bddeb6)

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 3 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 93% 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: Not scored.

Affected products

  • Linux · Linux

    • affected 117cd09ba52857a60dc5d7f61941046625d8ff5a – < 2f9aa8d42b7fc17621894456433ac07689fb4a21
    • affected 117cd09ba52857a60dc5d7f61941046625d8ff5a – < 5225122b9cad6b0c61e767fb2adea8c07da925be
    • affected 117cd09ba52857a60dc5d7f61941046625d8ff5a – < 6598ac1721c3a5543efdbcab579a8561268d7ce1
    • affected 117cd09ba52857a60dc5d7f61941046625d8ff5a – < f16218689b41efcbc491207cd7716477b1223879
    • affected 117cd09ba52857a60dc5d7f61941046625d8ff5a – < df1582c0a101e2e2f133dd331d2a3258bb6a7518
    • affected 117cd09ba52857a60dc5d7f61941046625d8ff5a – < c726c8bbee5115dad37fa7867136ebaa50690331
    • affected 117cd09ba52857a60dc5d7f61941046625d8ff5a – < f8a9262c7a6fc2de9802e14b0228114f0333869e
  • Linux · Linux

    • affected 5.12
    • unaffected < 5.12
    • unaffected 5.15.217 – ≤ 5.15.*
    • unaffected 6.1.184 – ≤ 6.1.*
    • unaffected 6.6.151 – ≤ 6.6.*
    • unaffected 6.12.103 – ≤ 6.12.*
    • unaffected 6.18.44 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .