# CVE-2026-97483: usb: core: hcd: fix possible deadlock in rh control transfers

> A deadlock in the Linux kernel USB core can cause a denial of service when handling root hub control transfers during device resets.

- **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:** 24 Sep 2026
- **Updated:** 3 Oct 2026
- **Also known as:** AZL-103880, BELL-CVE-2026-97483, DEBIAN-CVE-2026-97483, GHSA-47j5-5c6r-5qfh, UBUNTU-CVE-2026-97483

## What is CVE-2026-97483?

CVE-2026-97483 is a vulnerability in Linux, published on 24 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: hcd: fix possible deadlock in rh control transfers

>From within the SCSI error handler memory allocations must not
trigger IO. Handling errors in UAS and the storage driver may
involve resetting a device. The thread doing the reset itself
relies on VM magic. However, that is insufficient, as resetting
a device involves resuming it. Resumption as well as resetting
involves conrol transfers to the parent of the device to be reset.
That may be a root hub. Hence usbcore must heed the flags passed
to usb_submit_urb() processing control transfers to root hubs.

The problem exist since the storage driver has been merged.

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


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

Apply the vendor's patch.

## Is CVE-2026-97483 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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