# CVE-2026-80826: USB: c67x00: fix use-after-free in c67x00_add_iso_urb()

> A use-after-free in the Linux kernel c67x00 USB driver allows local attackers to cause denial of service or execute arbitrary code.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-99611, BELL-CVE-2026-80826, DEBIAN-CVE-2026-80826, GHSA-24fg-x37m-25c7, UBUNTU-CVE-2026-80826

## What is CVE-2026-80826?

CVE-2026-80826 is an use after free vulnerability in Linux, published on 4 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: c67x00: fix use-after-free in c67x00_add_iso_urb()

When TD creation fails for the last packet of an isochronous URB,
c67x00_add_iso_urb() gives the URB back before updating the endpoint
scheduling state.

c67x00_giveback_urb() frees the URB private data, and the completion
callback may release the final URB reference. The following accesses to
urbp->ep_data, urb->interval, and urbp->cnt can therefore use freed
memory.

Update next_frame and cnt before giving back the failed final packet,
making the giveback the last operation that uses the URB and its private
data.

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


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

Apply the vendor's patch.

## Is CVE-2026-80826 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80826 is an use after free vulnerability in Linux, published on 4 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-80826 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-80826/ (Markdown: https://insights.sbomify.com/CVE-2026-80826/index.md)
```

## Sources

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

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