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

Status: published. Published: 2026-08-15. Updated: 2026-11-06.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ 0613ad2401f88bdeae5594c30afe318e93b14676; < face65f80c6946c631ca3490b4ebd2c016a4fd2c (affected, git); ≥ 0613ad2401f88bdeae5594c30afe318e93b14676; < 6c66653dac9b25272d5fd4ed42a34aa5249e16df (affected, git); ≥ 0613ad2401f88bdeae5594c30afe318e93b14676; < 5b82af744e06cd741938c3da54fdbe564a7e52d9 (affected, git); ≥ 0613ad2401f88bdeae5594c30afe318e93b14676; < 618cf6b139503ec18ef93ffd663396aaf99b763a (affected, git); ≥ 0613ad2401f88bdeae5594c30afe318e93b14676; < a3b5f242997a3be7404112fd48784881560aea57 (affected, git); 41ed46bdbd2878cd6567abe0974a445f8b1b8ec8 (affected, git); 25f05d762ca5e1c685002a53dd44f68e78ca3feb (affected, git); a46e681151bbdacdf6b89ee8c4e5bad0555142bb (affected, git); 3b29f8769d32016b2d89183db4d80c7a71b7e35e (affected, git); 3049a3b927a40d89d4582ff1033cd7953be773c7 (affected, git); afc898019e7bf18c5eb7a0ac19852fcb1b341b3c (affected, git); c9e85979b59cb86f0a15defa8199d740e2b36b90 (affected, git); 2044b2ea77945f372ef161d1bbf814e471767ff2 (affected, git); ≥ 4.9.337; < 4.10 (affected, semver); ≥ 4.14.303; < 4.15 (affected, semver); ≥ 4.19.270; < 4.20 (affected, semver); ≥ 5.4.229; < 5.5 (affected, semver); ≥ 5.10.163; < 5.11 (affected, semver); ≥ 5.15.86; < 5.16 (affected, semver); ≥ 6.0.16; < 6.1 (affected, semver); ≥ 6.1.2; < 6.2 (affected, semver). Source: CNA: Linux
- Linux / Linux: 6.2 (affected); ≥ 0; < 6.2 (unaffected, semver); ≥ 6.6.160; ≤ 6.6.* (unaffected, semver); ≥ 6.12.114; ≤ 6.12.* (unaffected, semver); ≥ 6.18.42; ≤ 6.18.* (unaffected, semver); ≥ 7.1.5; ≤ 7.1.* (unaffected, semver); ≥ 7.2; ≤ * (unaffected, original_commit_for_fix). Source: CNA: Linux

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: 0.22% as of 2026-11-06; percentile 12.51%

- SSVC: exploitation none; automatable no; technical impact partial; source ADP: CISA-ADP

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/face65f80c6946c631ca3490b4ebd2c016a4fd2c (CNA: Linux)

- https://git.kernel.org/stable/c/6c66653dac9b25272d5fd4ed42a34aa5249e16df (CNA: Linux)

- https://git.kernel.org/stable/c/5b82af744e06cd741938c3da54fdbe564a7e52d9 (CNA: Linux)

- https://git.kernel.org/stable/c/618cf6b139503ec18ef93ffd663396aaf99b763a (CNA: Linux)

- https://git.kernel.org/stable/c/a3b5f242997a3be7404112fd48784881560aea57 (CNA: Linux)

- https://git.kernel.org/stable/c/5b82af744e06cd741938c3da54fdbe564a7e52d9 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/618cf6b139503ec18ef93ffd663396aaf99b763a (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/6c66653dac9b25272d5fd4ed42a34aa5249e16df (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/a3b5f242997a3be7404112fd48784881560aea57 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/face65f80c6946c631ca3490b4ebd2c016a4fd2c (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2026-72073; retrieved 2026-11-06; source updated 2026-11-06

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72073; retrieved 2026-11-06; source updated 2026-11-06

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-72073; retrieved 2026-11-06; source updated Not reported

Revision: ba3bbb4f3939357c6a44324e7990f478d0a41bdfe6937d1a42adf78a9fc39596

Canonical: https://y2.dev/cve/CVE-2026-72073

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.