mmc: core: Cancel SDIO IRQ work before freeing host
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 682696605c7093d2800c498c04166831e5aedf87 · < 6feadbecdae60a6324c967f3b1493741083793a3| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
mmc: core: Cancel SDIO IRQ work before freeing host
A host controller that uses sdio_signal_irq() schedules host->sdio_irq_work from its interrupt handler. That work is only cancelled on the suspend path (mmc_sdio_suspend()), not on the remove/free path, so a worker armed just before the controller freed its IRQ can run after mmc_host_classdev_release() has freed the host and dereference it through container_of().
Cancel host->sdio_irq_work in mmc_free_host(), like the existing host->detect drain added by commit 1036f69e2513 ("mmc: core: Cancel delayed work before releasing host").
This issue was found by an in-house static analysis tool.
From the CVE record · Linux
The Linux kernel MMC core can leave SDIO IRQ work queued after freeing a host controller. If a controller using sdio_signal_irq() schedules work just before removal, the worker can dereference the freed host. The input does not specify an attacker access path, authentication requirement, or user interaction.
Operators running Linux kernels with host controllers that use sdio_signal_irq() should check their kernel version; affected versions are not specified.