CVE-2026-93234

Unknown

Last modified

CVE-2026-93234 is a vulnerability of currently unknown severity. 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..

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.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 40e1a70b4aedf2859a1829991b48ef0ebe650bf2, < 676f1fb3632bbc9ce83be7938e93fe6bfc9510fd; >= 40e1a70b4aedf2859a1829991b48ef0ebe650bf2, < 06fcaf21c18ac88f57fee3803554f48c6026b95f; >= 40e1a70b4aedf2859a1829991b48ef0ebe650bf2, < 082e378886547b5b1c4075ed307f7c68547868dc; >= 40e1a70b4aedf2859a1829991b48ef0ebe650bf2, < 70cffc31a380b3eae45027101647aa94c242aa0e; >= 40e1a70b4aedf2859a1829991b48ef0ebe650bf2, < 72a95df6bbc7d20c7af1e39d86b3e910cccd01ad; >= 40e1a70b4aedf2859a1829991b48ef0ebe650bf2, < eab46d9629807db1b5647d17227e16110a18227f; >= 40e1a70b4aedf2859a1829991b48ef0ebe650bf2, < da1ea35fea67ad841f4ada28dd61b41be65e5437
LinuxLinux5.13

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-93234?
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.
How severe is CVE-2026-93234?
Severity scoring for CVE-2026-93234 is pending analysis.
How do I fix CVE-2026-93234?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-93234?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST