# CVE-2026-98762: USB: dwc2: shut down wakeup timer before freeing HCD state

> A use-after-free in the Linux kernel DWC2 USB driver allows local attackers to cause a denial of service or potentially execute code by triggering a race condition during HCD removal.

- **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:** 18 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-108869, BELL-CVE-2026-98762, DEBIAN-CVE-2026-98762, GHSA-g24x-rpv9-j8mw, UBUNTU-CVE-2026-98762

## What is CVE-2026-98762?

CVE-2026-98762 is an use after free vulnerability in Linux, published on 18 Oct 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: dwc2: shut down wakeup timer before freeing HCD state

dwc2_wakeup_detected() accesses the DWC2 host state and can rearm the
wakeup timer.  dwc2_hcd_free() currently deletes the timer only after
freeing host-owned state, and timer_delete() does not synchronize a
callback or prevent it from being queued again.

Stop and shut down the timer in dwc2_hcd_release(), before the HCD
resources are freed.  This covers both the HCD initialization error path
and normal HCD removal.

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


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

Apply the vendor's patch.

## Is CVE-2026-98762 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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