Vulnerability · Published Aug 15, 2026 · Assigned by Linux

CVE-2026-72073mmc: vub300: fix use-after-free on probe failure

Unrated

In plain English

A security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 13% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 87.5% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: mmc: vub300: fix use-after-free on probe failure The vub300 driver lifetime-manages its controller state using vub300->kref, with vub300_delete() freeing the mmc host when the last reference is dropped. The probe error path after the inactivity timer has been armed still bypasses that lifetime rule, however, and falls through to mmc_free_host() directly if mmc_add_host() fails. The race window is between arming the inactivity timer and reaching the probe error unwind after mmc_add_host() fails: probe thread timer/workqueue ------------ --------------- kref_init(&vub300->kref) ref = 1 kref_get(&vub300->kref) ref = 2, timer ref add_timer(inactivity_timer) fires after one second | | race window |<----------------------------------------------------> | mmc_add_host(mmc) inactivity timer fires vub300_queue_dead_work() kref_get() ref = 3 queue_work(deadwork) mmc_add_host() fails timer_delete_sync() mmc_free_host(mmc) frees vub300 deadwork runs use-after-free The inactivity timeout is one second, so this would require mmc_add_host() to both fail and take more than one second to do so. This is unlikely to happen in practice, but the error path is still wrong. timer_delete_sync() only waits for the timer callback itself. It does not flush deadwork that the callback may already have queued. As a result, queued deadwork can still hold a kref while the probe error path directly frees the backing mmc host, including the vub300 storage. Fix this by using the same lifetime mechanism as disconnect. Clear vub300->interface so that the timer callback and any queued deadwork return early and drop their references, then drop the initial probe reference and return without falling through to err_free_host.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linuxno fix listedDEBIAN-CVE-2026-72073
Debian:13linux6.12.115-2DEBIAN-CVE-2026-72073
Debian:14linux7.1.5-1DEBIAN-CVE-2026-72073
Ubuntu:22.04:LTSlinux5.15.0-202.212UBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2026-72073
Ubuntu:26.04:LTSlinux7.0.0-38.38UBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-aws5.15.0-1119.126UBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-72073
Ubuntu:26.04:LTSlinux-aws7.0.0-1014.14UBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-aws-7.07.0.0-1014.14~24.04.1UBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-azure5.15.0-1125.134UBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-72073
Ubuntu:26.04:LTSlinux-azure7.0.0-1017.17UBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-azure-7.07.0.0-1017.17~24.04.1UBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1124.133UBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-72073
Ubuntu:26.04:LTSlinux-azure-fde7.0.0-1016.16UBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-azure-fde-7.07.0.0-1016.16~24.04.1UBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-gcp5.15.0-1120.130UBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-72073
Ubuntu:26.04:LTSlinux-gcp7.0.0-1014.14UBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-gcp-7.07.0.0-1014.14~24.04.1UBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-gke5.15.0-1115.121UBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-72073
Ubuntu:26.04:LTSlinux-gke7.0.0-1008.9UBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1102.110UBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-38.38~24.04.4UBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-ibm5.15.0-1113.117UBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-72073
Ubuntu:26.04:LTSlinux-ibm7.0.0-1015.15UBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1114.120UBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-kvm5.15.0-1111.116UBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-197.207UBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1114.115UBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-72073
Ubuntu:26.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-nvidia-7.07.0.0-1024.25~24.04.1UBUNTU-CVE-2026-72073
Ubuntu:26.04:LTSlinux-nvidia-bos7.0.0-2022.23UBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1070.72UBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1059.59UBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-72073
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1015.15UBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-oracle5.15.0-1116.122UBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-72073
Ubuntu:26.04:LTSlinux-oracle7.0.0-1013.13UBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-oracle-7.07.0.0-1013.13~24.04.1UBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-72073
Ubuntu:26.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-72073
Ubuntu:26.04:LTSlinux-realtime7.0.0-38.38.1UBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-72073
Ubuntu:26.04:LTSlinux-riscv7.0.0-38.38.1UBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-riscv-7.07.0.0-38.38.1~24.04.1UBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2026-72073
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-72073
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2026-72073

Affected products (as reported)

VendorProductVersions
Linux Linux 0613ad2401f88bdeae5594c30afe318e93b14676 – before face65f80c6946c631ca3490b4ebd2c016a4fd2c0613ad2401f88bdeae5594c30afe318e93b14676 – before 6c66653dac9b25272d5fd4ed42a34aa5249e16df0613ad2401f88bdeae5594c30afe318e93b14676 – before 5b82af744e06cd741938c3da54fdbe564a7e52d90613ad2401f88bdeae5594c30afe318e93b14676 – before 618cf6b139503ec18ef93ffd663396aaf99b763a0613ad2401f88bdeae5594c30afe318e93b14676 – before a3b5f242997a3be7404112fd48784881560aea5741ed46bdbd2878cd6567abe0974a445f8b1b8ec825f05d762ca5e1c685002a53dd44f68e78ca3feba46e681151bbdacdf6b89ee8c4e5bad0555142bb
Linux Linux 6.2

References