linux
Affected
- introduced
0(ecosystem)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: CVE-2026-72073
The record has no summary.
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.
Not rated by the source.
0 (ecosystem)None listed
No fixed version is listed.
0, fixed 6.12.115-2 (ecosystem)6.12.115-2
6.12.115-2sudo apt-get update && sudo apt-get upgradeThis command upgrades the distribution's packages. Compare the fixed version with the version you have installed.
0, fixed 7.1.5-1 (ecosystem)7.1.5-1
7.1.5-1sudo apt-get update && sudo apt-get upgradeThis command upgrades the distribution's packages. Compare the fixed version with the version you have installed.
0, fixed 6.12.115-2~deb12u1 (ecosystem)6.12.115-2~deb12u1
6.12.115-2~deb12u1sudo apt-get update && sudo apt-get upgradeThis command upgrades the distribution's packages. Compare the fixed version with the version you have installed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: Debian Security Tracker (converted by OSV.dev)
Debian Security Tracker, converted to OSV by OSV.dev.