Answer in brief
CVE-2026-31650 records a Unknown severity vulnerability in mmc: vub300: fix use-after-free on disconnect. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=117a9c589ce0cf68065c007a02fd94da01e1181a <4b5251eebc2b1dedbb33fedf1b1109fea161b846 || >=dcfdd698dc521c6046e9b80c16281575efb25d23 <ea7468f61be033f4e18b95f2912010ed1d175d75 || >=dcfdd698dc521c6046e9b80c16281575efb25d23 <ef0448c569b37ceabdd038e9faa311e5179127b0 || >=dcfdd698dc521c6046e9b80c16281575efb25d23 <8f4d20a710225ec7a565f6a0459862d3b1f32330 | 4b5251eebc2b1dedbb33fedf1b1109fea161b846, ea7468f61be033f4e18b95f2912010ed1d175d75, ef0448c569b37ceabdd038e9faa311e5179127b0, 8f4d20a710225ec7a565f6a0459862d3b1f32330 |
| Linux/Linuxgeneric | 6.17 | Not reported |
Published upstream
Apr 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 21, 2026
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.
Quoted source text, attributed separately from HOL analysis.