# CVE-2026-93234: drm/gud: validate TV mode names before creating enum property

> A malicious USB display device can trigger an out-of-bounds read in the Linux kernel DRM driver, potentially causing a crash or leaking memory.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-93234, DEBIAN-CVE-2026-93234, GHSA-mh3c-9rpg-gxv8, UBUNTU-CVE-2026-93234

## What is CVE-2026-93234?

CVE-2026-93234 is a memory corruption vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-93234?


## How do I fix CVE-2026-93234?

Apply the vendor's patch.

## Is CVE-2026-93234 being exploited?

There is no known exploitation of CVE-2026-93234 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93234 and fix it if it is affected.

What it is: CVE-2026-93234 is a memory corruption vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93234 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93234/ (Markdown: https://insights.sbomify.com/CVE-2026-93234/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93234
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93234
- OSV: https://osv.dev/vulnerability/CVE-2026-93234

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93234/
Summaries are generated and may contain mistakes; the official description above is the record.