# CVE-2026-68366: usb: gadget: uvc: clamp SEND_RESPONSE length to the response buffer

> 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.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** BELL-CVE-2026-68366, DEBIAN-CVE-2026-68366, GHSA-hxh7-878r-vrmm, UBUNTU-CVE-2026-68366

## What is CVE-2026-68366?

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.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

usb: gadget: uvc: clamp SEND_RESPONSE length to the response buffer

uvc_send_response() builds the UVC control response from a user-supplied
struct uvc_request_data:

	req->length = min_t(unsigned int, uvc->event_length, data->length);
	...
	memcpy(req->buf, data->data, req->length);

req->length is clamped to uvc->event_length, which is taken from the
host control request wLength (up to UVC_MAX_REQUEST_SIZE, 64), and to
data->length, which comes from the UVCIOC_SEND_RESPONSE ioctl and is
only checked for being negative.  The source buffer data->data is only
60 bytes, so a response with uvc->event_length and data->length both
greater than 60 makes memcpy() read past the end of data->data.

Clamp req->length to sizeof(data->data) as well.

## Which versions are affected by CVE-2026-68366?


## How do I fix CVE-2026-68366?

Apply the vendor's patch.

## Is CVE-2026-68366 being exploited?

There is no known exploitation of CVE-2026-68366 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-68366 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2026-68366 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-68366/ (Markdown: https://insights.sbomify.com/CVE-2026-68366/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-68366
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-68366
- OSV: https://osv.dev/vulnerability/CVE-2026-68366

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-68366/
Summaries are generated and may contain mistakes; the official description above is the record.