Quick answers
- Is CVE-2026-93234 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93234 being exploited in the wild.
- How severe is CVE-2026-93234?
- Informational severity, published 24 September 2026.
- Which products and versions are affected?
- Unknown Linux kernel from approximately 5.9 (when GUD driver was added) through 6.12+.
- Is there a fix for CVE-2026-93234?
- A patch was published on 2026-09-14. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-93234 attacked?
- It is attacked from the adjacent network, in an operating system.
- Am I affected by CVE-2026-93234?
- Check whether you run Unknown Linux kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The gud_connector_add_tv_mode() function in the DRM GUD driver processes TV mode names from device responses without verifying they are NUL-terminated within their fixed-size buffer slots. When strlen() is called on an unterminated buffer, it reads past the allocated boundary. The fix validates that each mode name contains a NUL terminator before passing it to drm_property_add_enum(), rejecting malformed responses with -EIO.
Affected products
- <UNKNOWN> Linux kernel from approximately 5.9 (when GUD driver was added) through 6.12+
Timeline
- 2026-09-24: disclosed
- 2026-09-14: patched