mmc: mxcmmc: cancel data work and watchdog on remove
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel e2948c4232209e87c861a680f20f1e3cf8a57fec, Kernel 23383e0578b58ba2dc0730cf9f7806bd66bf859a, Kernel 314966b490323bdcfd3162a1398b00e587e0ced4 and 12 more.
In the Linux kernel, the following vulnerability has been resolved: mmc: mxcmmc: cancel data work and watchdog on remove mxcmci_remove() frees the host through the devm tail, but neither it nor mmc_remove_host() drains the driver's own asynchronous state. host->watchdog, a 10 s timer armed on the DMA path in mxcmci_setup_data(), is deleted only by the DMA- and IRQ-complete paths, which the remove path does not explicitly drain; it can therefore fire after the host is freed and dereference it in mxcmci_watchdog(). host->datawork, armed from the IRQ handler on the PIO path, is not cancelled by the remove path either. Free the devm-registered IRQ, then cancel datawork and delete the watchdog in mxcmci_remove(), before dma_release_channel(). Freeing the IRQ first keeps a trailing handler from re-arming datawork between the cancel and the host free. Both callbacks are non-self-rearming. This issue was found by an in-house static analysis tool.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=f6ad0a481342223b2e7ae9f55b154e14f1391ada <e2948c4232209e87c861a680f20f1e3cf8a57fec, >=f6ad0a481342223b2e7ae9f55b154e14f1391ada <23383e0578b58ba2dc0730cf9f7806bd66bf859a, >=f6ad0a481342223b2e7ae9f55b154e14f1391ada <314966b490323bdcfd3162a1398b00e587e0ced4, >=f6ad0a481342223b2e7ae9f55b154e14f1391ada <740f595f8ad678cb4d79f13edd12851df2492bdd, >=f6ad0a481342223b2e7ae9f55b154e14f1391ada <a1ff367e0dc961d73707add508a95df5c3509bd1, >=f6ad0a481342223b2e7ae9f55b154e14f1391ada <ae10838a7cdf0e54caa9d0a4f488704fd04e7f01, >=f6ad0a481342223b2e7ae9f55b154e14f1391ada <d3641afe6ee76d852834a34ef0669eefced32752, >=f6ad0a481342223b2e7ae9f55b154e14f1391ada <d3a421c82412344022982d5b91ba23194a0a6f29, =3.7 | e2948c4232209e87c861a680f20f1e3cf8a57fec, 23383e0578b58ba2dc0730cf9f7806bd66bf859a, 314966b490323bdcfd3162a1398b00e587e0ced4, 740f595f8ad678cb4d79f13edd12851df2492bdd, a1ff367e0dc961d73707add508a95df5c3509bd1, ae10838a7cdf0e54caa9d0a4f488704fd04e7f01, d3641afe6ee76d852834a34ef0669eefced32752, d3a421c82412344022982d5b91ba23194a0a6f29 |
| linux-kernel: Kernel | >=5.11.0 <5.15.222, >=5.16.0 <6.1.189, >=6.13.0 <6.18.54, >=6.19.0 <7.2.8, >=6.2.0 <6.6.158, >=6.7.0 <6.12.112, >=3.7.0 <5.10.271 | 5.15.222, 6.1.189, 6.18.54, 7.2.8, 6.6.158, 6.12.112, 5.10.271 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket