{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93234 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-93234 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-93234 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-93234/ (Markdown: https://insights.sbomify.com/CVE-2026-93234/index.md)","id":"CVE-2026-93234","markdown":"https://insights.sbomify.com/CVE-2026-93234/index.md","name":"CVE-2026-93234","record":{"aliases":["BELL-CVE-2026-93234","DEBIAN-CVE-2026-93234","GHSA-mh3c-9rpg-gxv8","UBUNTU-CVE-2026-93234"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel DRM","requires_auth":"none","summary":"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.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/gud: validate TV mode names before creating enum property\n\nThe GUD protocol returns TV mode names as fixed-size\nGUD_CONNECTOR_TV_MODE_NAME_LEN entries and requires each name to be\nNUL-terminated.\n\ngud_connector_add_tv_mode() currently passes each fixed-size entry\ndirectly to drm_mode_create_tv_properties_legacy(), which eventually\nreaches drm_property_add_enum() and strlen(). If a device returns an\nentry without a terminating NUL byte, strlen() reads past the end of\nthe slot and can run beyond the allocated buffer, triggering an\nout-of-bounds read.\n\nValidate that each returned TV mode name contains a NUL terminator\nwithin its fixed-size slot before passing it to the DRM property code.\nIf a malformed entry is found, reject the device response with -EIO.\n\nThis fixes the out-of-bounds read without changing the handling of\nvalid devices, and avoids silently truncating malformed protocol data.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"drm/gud: validate TV mode names before creating enum property","id":"CVE-2026-93234","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"f2fs: fix to zero post-EOF data when extending file size","id":"CVE-2026-93235"},"packages":[],"prev":{"headline":"drm/nouveau/dmem: fix callocated underflow on large folio split","id":"CVE-2026-93233"},"products":["Linux"],"published":"2026-09-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"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.","url":"https://insights.sbomify.com/CVE-2026-93234/"}