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-93234drm/gud: validate TV mode names before creating enum property

Description

In the Linux kernel, the following vulnerability has been resolved: drm/gud: validate TV mode names before creating enum property The GUD protocol returns TV mode names as fixed-size GUD_CONNECTOR_TV_MODE_NAME_LEN entries and requires each name to be NUL-terminated. gud_connector_add_tv_mode() currently passes each fixed-size entry directly to drm_mode_create_tv_properties_legacy(), which eventually reaches drm_property_add_enum() and strlen(). If a device returns an entry without a terminating NUL byte, strlen() reads past the end of the slot and can run beyond the allocated buffer, triggering an out-of-bounds read. Validate that each returned TV mode name contains a NUL terminator within its fixed-size slot before passing it to the DRM property code. If a malformed entry is found, reject the device response with -EIO. This fixes the out-of-bounds read without changing the handling of valid devices, and avoids silently truncating malformed protocol data.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 25 days 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.21% · top 89% of all CVEs (18 Nov 2026)
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 40e1a70b4aedf2859a1829991b48ef0ebe650bf2 – < 676f1fb3632bbc9ce83be7938e93fe6bfc9510fd
    • affected 40e1a70b4aedf2859a1829991b48ef0ebe650bf2 – < 06fcaf21c18ac88f57fee3803554f48c6026b95f
    • affected 40e1a70b4aedf2859a1829991b48ef0ebe650bf2 – < 082e378886547b5b1c4075ed307f7c68547868dc
    • affected 40e1a70b4aedf2859a1829991b48ef0ebe650bf2 – < 70cffc31a380b3eae45027101647aa94c242aa0e
    • affected 40e1a70b4aedf2859a1829991b48ef0ebe650bf2 – < 72a95df6bbc7d20c7af1e39d86b3e910cccd01ad
    • affected 40e1a70b4aedf2859a1829991b48ef0ebe650bf2 – < eab46d9629807db1b5647d17227e16110a18227f
    • affected 40e1a70b4aedf2859a1829991b48ef0ebe650bf2 – < da1ea35fea67ad841f4ada28dd61b41be65e5437
  • Linux · Linux

    • affected 5.13
    • unaffected < 5.13
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.51 – ≤ 6.18.*
    • unaffected 7.2.5 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .