mmc: mxcmmc: cancel data work and watchdog on remove
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From f6ad0a481342223b2e7ae9f55b154e14f1391ada · fixed in 740f595f8ad678cb4d79f13edd12851df2492bdd; From f6ad0a481342223b2e7ae9f55b154e14f1391ada · fixed in d3641afe6ee76d852834a34ef0669eefced32752; From f6ad0a481342223b2e7ae9f55b154e14f1391ada · fixed in 314966b490323bdcfd3162a1398b00e587e0ced4; From f6ad0a481342223b2e7ae9f55b154e14f1391ada · fixed in ae10838a7cdf0e54caa9d0a4f488704fd04e7f01; From f6ad0a481342223b2e7ae9f55b154e14f1391ada · fixed in a1ff367e0dc961d73707add508a95df5c3509bd1; From f6ad0a481342223b2e7ae9f55b154e14f1391ada · fixed in 23383e0578b58ba2dc0730cf9f7806bd66bf859a; From f6ad0a481342223b2e7ae9f55b154e14f1391ada · fixed in e2948c4232209e87c861a680f20f1e3cf8a57fec; From f6ad0a481342223b2e7ae9f55b154e14f1391ada · fixed in d3a421c82412344022982d5b91ba23194a0a6f29
- Linux Linux
3.7
- KernelLinux
From 3.7.0 · fixed in 5.10.271; From 5.11.0 · fixed in 5.15.222; From 5.16.0 · fixed in 6.1.189; From 6.2.0 · fixed in 6.6.158; From 6.7.0 · fixed in 6.12.112; From 6.13.0 · fixed in 6.18.54; From 6.19.0 · fixed in 7.2.8
References 8
git.kernel.org
- stable/c/740f595f8ad678cb4d79f13edd12851df2492bdd
- stable/c/d3641afe6ee76d852834a34ef0669eefced32752
- stable/c/314966b490323bdcfd3162a1398b00e587e0ced4
- stable/c/ae10838a7cdf0e54caa9d0a4f488704fd04e7f01
- stable/c/a1ff367e0dc961d73707add508a95df5c3509bd1
- stable/c/23383e0578b58ba2dc0730cf9f7806bd66bf859a
- stable/c/e2948c4232209e87c861a680f20f1e3cf8a57fec
- stable/c/d3a421c82412344022982d5b91ba23194a0a6f29