https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 09 Oct 2026 22:32:43 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-98210 <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2026-98210 https://cve.radiocsirt.org/vuln/euvd-2026-383321 EUVD-2026-383321 https://cve.radiocsirt.org/vuln/euvd-2026-383321 https://cve.radiocsirt.org/vuln/fkie_cve-2026-98210 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mmc: mxcmmc: cancel data work and watchdog on remove</p> <p>mxcmci_remove() frees the host through the devm tail, but neither it nor mmc_remove_host() drains the driver&#39;s own asynchronous state. host-&gt;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-&gt;datawork, armed from the IRQ handler on the PIO path, is not cancelled by the remove path either.</p> <p>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.</p> <p>This issue was found by an in-house static analysis tool.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mmc: mxcmmc: cancel data work and watchdog on remove</p> <p>mxcmci_remove() frees the host through the devm tail, but neither it nor mmc_remove_host() drains the driver&#39;s own asynchronous state. host-&gt;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-&gt;datawork, armed from the IRQ handler on the PIO path, is not cancelled by the remove path either.</p> <p>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.</p> <p>This issue was found by an in-house static analysis tool.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-98210 https://cve.radiocsirt.org/vuln/ghsa-3899-r8v9-5w9h <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mmc: mxcmmc: cancel data work and watchdog on remove</p> <p>mxcmci_remove() frees the host through the devm tail, but neither it nor mmc_remove_host() drains the driver&#39;s own asynchronous state. host-&gt;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-&gt;datawork, armed from the IRQ handler on the PIO path, is not cancelled by the remove path either.</p> <p>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.</p> <p>This issue was found by an in-house static analysis tool.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mmc: mxcmmc: cancel data work and watchdog on remove</p> <p>mxcmci_remove() frees the host through the devm tail, but neither it nor mmc_remove_host() drains the driver&#39;s own asynchronous state. host-&gt;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-&gt;datawork, armed from the IRQ handler on the PIO path, is not cancelled by the remove path either.</p> <p>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.</p> <p>This issue was found by an in-house static analysis tool.</p> https://cve.radiocsirt.org/vuln/ghsa-3899-r8v9-5w9h https://cve.radiocsirt.org/vuln/msrc_cve-2026-98210 msrc_CVE-2026-98210 https://cve.radiocsirt.org/vuln/msrc_cve-2026-98210 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98210 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 247 more</p> <p>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&#39;s own asynchronous state. host-&gt;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-&gt;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.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 247 more</p> <p>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&#39;s own asynchronous state. host-&gt;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-&gt;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.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98210