CVE-2026-31650: Linux kernel · mmc: vub300: fix use-after-free on disconnect
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in ef0448c569b37ceabdd038e9faa311e5179127b0 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in ef0448c569b37ceabdd038e9faa311e5179127b0, ea7468f61be033f4e18b95f2912010ed1d175d75, 8f4d20a710225ec7a565f6a0459862d3b1f32330 +1
Exploitation evidence
Disclosed: evidence found.
CVE published 24 Apr 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 Linux kernel to ef0448c569b37ceabdd038e9faa311e5179127b0, ea7468f61be033f4e18b95f2912010ed1d175d75, 8f4d20a710225ec7a565f6a0459862d3b1f32330 or 4b5251eebc2b1dedbb33fedf1b1109fea161b846.
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– |
Description
In the Linux kernel, the following vulnerability has been resolved: mmc: vub300: fix use-after-free on disconnect The vub300 driver maintains an explicit reference count for the controller and its driver data and the last reference can in theory be dropped after the driver has been unbound. This specifically means that the controller allocation must not be device managed as that can lead to use-after-free. Note that the lifetime is currently also incorrectly tied the parent USB device rather than interface, which can lead to memory leaks if the driver is unbound without its device being physically disconnected (e.g. on probe deferral). Fix both issues by reverting to non-managed allocation of the controller.
References
- git.kernel.org/stable/c/4b5251eebc2b1dedbb33fedf1b1109fea161b846 (opens in a new tab)
- git.kernel.org/stable/c/ea7468f61be033f4e18b95f2912010ed1d175d75 (opens in a new tab)
- git.kernel.org/stable/c/ef0448c569b37ceabdd038e9faa311e5179127b0 (opens in a new tab)
- git.kernel.org/stable/c/8f4d20a710225ec7a565f6a0459862d3b1f32330 (opens in a new tab)