# CVE-2026-89733: usb: gadget: uvc: fix dangling pointers in uvc_function_bind() and uvc_function_unbind()

> A use-after-free vulnerability in the Linux kernel's USB gadget UVC driver allows attackers to potentially execute code or escalate privileges via dangling pointers.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 11 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-100431, BELL-CVE-2026-89733, DEBIAN-CVE-2026-89733, GHSA-p2g2-5xg5-fj3w, UBUNTU-CVE-2026-89733

## What is CVE-2026-89733?

CVE-2026-89733 is a high-severity use after free vulnerability in Linux, published on 11 Sep 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: fix dangling pointers in uvc_function_bind() and uvc_function_unbind()

In uvc_function_bind() error path, we use usb_ep_free_request which
uses uvc->control_req but does not set it to NULL afterwards. Thus,
uvc->control_req is a dangling pointer causing a UAF. Also we do not set
the uvc->control_buf pointer to NULL after freeing it, which is another
dangling pointer. Fix it by setting uvc->control_req to NULL after we run
usb_ep_free_request() and uvc->control_buf to NULL after kfree. Do the
same for uvc_function_unbind().

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


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

Apply the vendor's patch.

## Is CVE-2026-89733 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89733 is a high-severity use after free vulnerability in Linux, published on 11 Sep 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-89733 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-89733/ (Markdown: https://insights.sbomify.com/CVE-2026-89733/index.md)
```

## Sources

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

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