# CVE-2024-36896: USB: core: Fix access violation during port device removal

> A null pointer dereference in the Linux kernel USB core allows local attackers to cause a system crash during port device removal.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 May 2024
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2024-36896, DEBIAN-CVE-2024-36896, UBUNTU-CVE-2024-36896

## What is CVE-2024-36896?

CVE-2024-36896 is a critical vulnerability in Linux kernel, published on 30 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

USB: core: Fix access violation during port device removal

Testing with KASAN and syzkaller revealed a bug in port.c:disable_store():
usb_hub_to_struct_hub() can return NULL if the hub that the port belongs to
is concurrently removed, but the function does not check for this
possibility before dereferencing the returned value.

It turns out that the first dereference is unnecessary, since hub->intfdev
is the parent of the port device, so it can be changed easily.  Adding a
check for hub == NULL prevents further problems.

The same bug exists in the disable_show() routine, and it can be fixed the
same way.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2024-36896?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-36896?

Apply the vendor's patch.

## Is CVE-2024-36896 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-36896 and fix it if it is affected.

What it is: CVE-2024-36896 is a critical vulnerability in Linux kernel, published on 30 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-36896 in the wild and no public exploit code.

Affected product: Linux kernel. 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-2024-36896/ (Markdown: https://insights.sbomify.com/CVE-2024-36896/index.md)
```

## Sources

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

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