{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93067 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93067 is a memory corruption vulnerability in Linux, published on 17 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-93067 and fix it if it is affected.\n\nWhat it is: CVE-2026-93067 is a memory corruption vulnerability in Linux, published on 17 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-93067 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-93067/ (Markdown: https://insights.sbomify.com/CVE-2026-93067/index.md)","id":"CVE-2026-93067","markdown":"https://insights.sbomify.com/CVE-2026-93067/index.md","name":"CVE-2026-93067","record":{"aliases":["AZL-102731","BELL-CVE-2026-93067","DEBIAN-CVE-2026-93067","GHSA-wpcc-v879-hj4w","UBUNTU-CVE-2026-93067"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A buffer overflow in the Linux kernel tc358767 DRM bridge driver allows local attackers to execute code or cause a denial of service via crafted AUX transfers.","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/bridge: tc358767: clamp the reported AUX read size to the request\n\ntc_aux_transfer() clamps an AUX read to the payload limit:\n\n\tsize_t size = min_t(size_t, DP_AUX_MAX_PAYLOAD_BYTES - 1, msg-\u003esize);\n\nAfter the transfer it replaces size with the byte count the controller\nreports in AUX_BYTES:\n\n\tif (size)\n\t\tsize = FIELD_GET(AUX_BYTES, auxstatus);\n\nAUX_BYTES is GENMASK(15, 8), so it can be up to 255. Nothing clamps it\nback to the request. tc_aux_read_data() reads that many bytes into the\n16-byte auxrdata stack buffer, then copies them into the caller buffer. A\nreported count of 255 makes the read run to 256 bytes and overruns both.\n\nThe controller should never report more than it was asked to transfer, so\nthis is defense in depth rather than a live hole. The reported count is\nonly lightly trusted, and the check is cheap. Clamp it back to the request,\nthe same way ti-sn65dsi86 does in commit aca58eac52b8 (\"drm/bridge:\nti-sn65dsi86: Never store more than msg-\u003esize bytes in AUX xfer\").","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/bridge: tc358767: clamp the reported AUX read size to the request","id":"CVE-2026-93067","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"drm/amd/display: Fix DM I2C teardown race","id":"CVE-2026-93068"},"packages":[],"prev":{"headline":"x86/mm/pat: Take cpa_lock around large-page collapse","id":"CVE-2026-93066"},"products":["Linux"],"published":"2026-09-17","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 buffer overflow in the Linux kernel tc358767 DRM bridge driver allows local attackers to execute code or cause a denial of service via crafted AUX transfers.","url":"https://insights.sbomify.com/CVE-2026-93067/"}