# CVE-2026-80830: usb: core: Add lock to usb_wakeup_notification()

> A race condition in the Linux kernel USB core allows local attackers to trigger a use-after-free, potentially causing a system crash.

- **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-99405, BELL-CVE-2026-80830, DEBIAN-CVE-2026-80830, GHSA-6h45-3gcw-mpwf, UBUNTU-CVE-2026-80830

## What is CVE-2026-80830?

CVE-2026-80830 is a 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: core: Add lock to usb_wakeup_notification()

Add a spin lock to usb_wakeup notification to prevent a race condition
with dereferencing freed memory. This could be hit by the xHCI driver as
it calls this function from an IRQ and could race with the
hub_disconnect() function, which properly grabs this lock to protect the
state of the device.

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


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

Apply the vendor's patch.

## Is CVE-2026-80830 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80830 is a 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-80830 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-80830/ (Markdown: https://insights.sbomify.com/CVE-2026-80830/index.md)
```

## Sources

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

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