# CVE-2026-90029: usb: storage: realtek_cr: fix use-after-free on disconnect

> A use-after-free vulnerability in the Linux kernel's Realtek USB storage driver allows local attackers to execute code or cause a denial of service via device disconnection.

- **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:** 16 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-101447, BELL-CVE-2026-90029, DEBIAN-CVE-2026-90029, GHSA-m7jg-4wjg-p9fx, UBUNTU-CVE-2026-90029

## What is CVE-2026-90029?

CVE-2026-90029 is an use after free vulnerability in Linux, published on 16 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: storage: realtek_cr: fix use-after-free on disconnect

realtek_cr_destructor() calls timer_delete() before the chip containing
the timer is freed. The timer callback may still be running and can
rearm itself, resulting in a use-after-free.

Use timer_shutdown_sync() to wait for the callback and prevent further
rearming. Do this unconditionally because ss_en may be changed after
the timer is armed.

Move timer_setup() into init_realtek_cr() so the timer is initialized
before any failure path can invoke the destructor.

Found by static analysis.

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


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

Apply the vendor's patch.

## Is CVE-2026-90029 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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