{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-68366 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-68366 is a memory corruption vulnerability in Linux, published on 10 Aug 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-68366 and fix it if it is affected.\n\nWhat it is: CVE-2026-68366 is a memory corruption vulnerability in Linux, published on 10 Aug 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-68366 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-68366/ (Markdown: https://insights.sbomify.com/CVE-2026-68366/index.md)","id":"CVE-2026-68366","markdown":"https://insights.sbomify.com/CVE-2026-68366/index.md","name":"CVE-2026-68366","record":{"aliases":["BELL-CVE-2026-68366","DEBIAN-CVE-2026-68366","GHSA-hxh7-878r-vrmm","UBUNTU-CVE-2026-68366"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel USB gadget","requires_auth":"low_privilege","summary":"A local attacker with USB gadget access can trigger a buffer over-read in the Linux kernel UVC driver, potentially leading to code execution or privilege escalation.","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\nusb: gadget: uvc: clamp SEND_RESPONSE length to the response buffer\n\nuvc_send_response() builds the UVC control response from a user-supplied\nstruct uvc_request_data:\n\n\treq-\u003elength = min_t(unsigned int, uvc-\u003eevent_length, data-\u003elength);\n\t...\n\tmemcpy(req-\u003ebuf, data-\u003edata, req-\u003elength);\n\nreq-\u003elength is clamped to uvc-\u003eevent_length, which is taken from the\nhost control request wLength (up to UVC_MAX_REQUEST_SIZE, 64), and to\ndata-\u003elength, which comes from the UVCIOC_SEND_RESPONSE ioctl and is\nonly checked for being negative.  The source buffer data-\u003edata is only\n60 bytes, so a response with uvc-\u003eevent_length and data-\u003elength both\ngreater than 60 makes memcpy() read past the end of data-\u003edata.\n\nClamp req-\u003elength to sizeof(data-\u003edata) as well.","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":"usb: gadget: uvc: clamp SEND_RESPONSE length to the response buffer","id":"CVE-2026-68366","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":"usb: gadget: f_tcm: synchronize delayed set_alt with teardown","id":"CVE-2026-68367"},"packages":[],"prev":{"headline":"USB: serial: io_edgeport: cap received transmit credits","id":"CVE-2026-68365"},"products":["Linux"],"published":"2026-08-10","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-08-19","vendors":["Linux"]},"summary":"A local attacker with USB gadget access can trigger a buffer over-read in the Linux kernel UVC driver, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-68366/"}