CVE-2026-31650·Kernel vulnerability
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.
- Severity
- high
- Software
- Kernel
- Fixed in
- 6.19.13
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.15% — higher than 4% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-31650 scores 7.8 on CVSS, so a successful attack would be serious — but at 0.15%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
Affected versions
From: 6.19
Until: 6.19.13
Fixed in: 6.19.13
How to fix this CVE
Update your Linux kernel to version 6.19.13 or later to resolve a use-after-free vulnerability in the vub300 MMC driver that can occur during device disconnect. This flaw affects kernel versions 6.19 through 6.19.12 and requires immediate patching to prevent potential memory corruption and system instability. Apply the update through your distribution's package manager and reboot your system to complete the remediation.
sudo dnf update kernel kernel-devel && sudo rebootDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check your current kernel version by running: uname -r
- Step 2: Verify if the vub300 driver is loaded by running: lsmod | grep vub300
- Step 3: Search system logs for memory corruption or use-after-free errors related to vub300: sudo journalctl -b | grep -i 'vub300\|use-after-free\|memory'
- Step 4: After updating, verify the new kernel version is running: uname -r (should show 6.19.13 or later)
FAQ
What is CVE-2026-31650?
This vulnerability is a use-after-free bug in the Linux kernel's vub300 MMC driver where memory can be accessed after it has been freed during device disconnection. This occurs due to improper reference counting and device-managed memory allocation in the driver.
Is CVE-2026-31650 being actively exploited?
No, this vulnerability is not currently listed on CISA's Known Exploited Vulnerabilities (KEV) catalog and no public exploits are available. However, it should still be patched promptly due to its high severity rating.
What versions of Kernel are affected by CVE-2026-31650?
Linux kernel versions 6.19 through 6.19.12 are vulnerable. Version 6.19.13 and later contain the fix.
How do I check if my server is vulnerable to CVE-2026-31650?
Run 'uname -r' to check your kernel version. If it shows 6.19 to 6.19.12, you are vulnerable. Additionally, run 'lsmod | grep vub300' to confirm if the affected driver is in use on your system.
Does Defensia detect CVE-2026-31650?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Kernel is installed on a monitored server, CVE-2026-31650 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-31650. Free for 1 server.
Get started free