Skip to main content

Linux EUVDEUVD-2026-86239

| CVE-2026-93234
2026-09-24 Linux GHSA-mh3c-9rpg-gxv8
View
Monitor Track and reassess. Why: No CVSS yet + weak signal (CWE or non-zero EPSS).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisCVE.org

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.

Affected VersionsENISA

Linux patch: 7.2.5
Linux patch: 7.3-rc2
Linux 40e1a70b4aedf2859a1829991b48ef0ebe650bf2 <72a95df6bbc7d20c7af1e39d86b3e910cccd01ad
Linux 40e1a70b4aedf2859a1829991b48ef0ebe650bf2 <70cffc31a380b3eae45027101647aa94c242aa0e
Linux 40e1a70b4aedf2859a1829991b48ef0ebe650bf2 <da1ea35fea67ad841f4ada28dd61b41be65e5437
Linux patch: 6.18.51
Linux patch: 6.6.157
Linux patch: 6.12.110
Linux 40e1a70b4aedf2859a1829991b48ef0ebe650bf2 <06fcaf21c18ac88f57fee3803554f48c6026b95f
Linux patch: 0
Linux 5.13
Linux patch: 5.15.221
Linux 40e1a70b4aedf2859a1829991b48ef0ebe650bf2 <676f1fb3632bbc9ce83be7938e93fe6bfc9510fd
Linux 40e1a70b4aedf2859a1829991b48ef0ebe650bf2 <082e378886547b5b1c4075ed307f7c68547868dc
Linux 40e1a70b4aedf2859a1829991b48ef0ebe650bf2 <eab46d9629807db1b5647d17227e16110a18227f
Linux patch: 6.1.188

Affected Packages

euvd linux no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Lifecycle Timeline

2
Patch available
Sep 24, 2026 - 17:18 EUVD
CVE Published
Sep 24, 2026 - 15:33 cve.org
UNKNOWN (no severity yet)

Threat Intelligence Overview

EPSS Score
0.2%
Top 91% exploitable
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity Not scored yet
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
No CVSS yet + weak signal (CWE or non-zero EPSS)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy