CVE-2026-90029: Linux kernel · usb: storage: realtek_cr: fix use-after-free on disconnect
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in cae9dbba6adae21a04a3bd045e07b489847ff2c6 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 17:16 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in cae9dbba6adae21a04a3bd045e07b489847ff2c6, c1e7e35100efffba7c9e1dfa76519d6cd323ba3d, 524d4257f741cd95eb85e2817c9c890928fcfef7 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 16 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
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.
References
- git.kernel.org/stable/c/c1e7e35100efffba7c9e1dfa76519d6cd323ba3d (opens in a new tab)
- git.kernel.org/stable/c/524d4257f741cd95eb85e2817c9c890928fcfef7 (opens in a new tab)
- git.kernel.org/stable/c/7c4e2f964c65dea4ea22386799d5fb10ef1e3e54 (opens in a new tab)
- git.kernel.org/stable/c/cae9dbba6adae21a04a3bd045e07b489847ff2c6 (opens in a new tab)
- git.kernel.org/stable/c/4ffee1aebb0c0ffcda9faffd17834ea9b00d42cc (opens in a new tab)