CVE-2026-31650
Last modified
CVE-2026-31650 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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.. EPSS estimates a 0.11% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.17.1, < 6.18.23 | — |
| Linux | Linux Kernel | >= 6.19, < 6.19.13 | — |
| Linux | Linux Kernel | 6.17 | — |
| Linux | Linux Kernel | 7.0 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-31650?
How severe is CVE-2026-31650?
How do I fix CVE-2026-31650?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-31645In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31646In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31647In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31648In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-31649In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-3165A vulnerability was determined in Tenda F453 1.0.0.3. Impact…8.8
- CVE-2026-31651In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31652In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-31653In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31654In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31655In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31656In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-31650?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST