# CVE-2026-97484: usbip: vhci_hcd: fix NULL deref in status_show_vhci

> A local attacker can cause a kernel crash via NULL pointer dereference in the USBIP vhci_hcd status handler when probe fails.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **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-104045, BELL-CVE-2026-97484, DEBIAN-CVE-2026-97484, GHSA-gwrg-cchr-q69g, UBUNTU-CVE-2026-97484

## What is CVE-2026-97484?

CVE-2026-97484 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:

usbip: vhci_hcd: fix NULL deref in status_show_vhci

platform_get_drvdata() can return NULL if a VHCI host controller's
probe failed (e.g. due to USB bus number exhaustion). status_show_vhci()
checked for a NULL pdev but not for a NULL hcd returned by
platform_get_drvdata(). Passing NULL to hcd_to_vhci_hcd() does not
return NULL - it returns a pointer offset of 0x260, causing a NULL
pointer dereference when that value is subsequently dereferenced.

Add a NULL check on hcd before calling hcd_to_vhci_hcd(). Move
status_show_not_ready() above status_show_vhci() to make it callable
from the new error path without a forward declaration.

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


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

Apply the vendor's patch.

## Is CVE-2026-97484 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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