mmc: vub300: fix use-after-free on disconnect
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.23, 6.19.13
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 117a9c589ce0cf68065c007a02fd94da01e1181a · fixed in 4b5251eebc2b1dedbb33fedf1b1109fea161b846; From dcfdd698dc521c6046e9b80c16281575efb25d23 · fixed in ea7468f61be033f4e18b95f2912010ed1d175d75; From dcfdd698dc521c6046e9b80c16281575efb25d23 · fixed in ef0448c569b37ceabdd038e9faa311e5179127b0; From dcfdd698dc521c6046e9b80c16281575efb25d23 · fixed in 8f4d20a710225ec7a565f6a0459862d3b1f32330
- Linux Linux
6.17
- KernelLinux
From 6.17.0 · fixed in 6.18.23; From 6.19.0 · fixed in 6.19.13