# CVE-2026-64454: usb: dwc3: run gadget disconnect from sleepable suspend context

> A locking bug in the Linux kernel DWC3 USB driver causes a kernel panic when a sleepable disconnect callback is invoked during suspend, leading to denial of service.

- **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:** 25 Jul 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-64454, DEBIAN-CVE-2026-64454, GHSA-c564-jfpf-wjrh, ROOT-OS-UBUNTU-2204-CVE-2026-64454, UBUNTU-CVE-2026-64454

## What is CVE-2026-64454?

CVE-2026-64454 is a denial of service vulnerability in Linux, published on 25 Jul 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: dwc3: run gadget disconnect from sleepable suspend context

dwc3_gadget_suspend() takes dwc->lock with IRQs disabled and then calls
dwc3_disconnect_gadget().  For async callbacks that helper only uses
plain spin_unlock()/spin_lock(), so the gadget ->disconnect() callback
still runs with IRQs disabled and any sleepable callback trips Lockdep.

This issue was found by our static analysis tool and then manually
reviewed against the current tree.

The grounded PoC kept the dwc3_gadget_suspend() ->
dwc3_disconnect_gadget() -> gadget_driver->disconnect() chain, and
Lockdep reported:

  BUG: sleeping function called from invalid context
  gadget_disconnect+0x21/0x39 [vuln_msv]
  dwc3_gadget_suspend.constprop.0+0x2b/0x42 [vuln_msv]

Keep the disconnect callback selection in one common helper, but add a
sleepable suspend-side wrapper which snapshots the callback under
dwc->lock and then runs it after spin_unlock_irqrestore().  The regular
event path still uses the existing spin_unlock()/spin_lock() window.

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


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

Apply the vendor's patch.

## Is CVE-2026-64454 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-64454 is a denial of service vulnerability in Linux, published on 25 Jul 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-64454 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-64454/ (Markdown: https://insights.sbomify.com/CVE-2026-64454/index.md)
```

## Sources

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

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