<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 16:43:47 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80556 — mmc: atmel-mci: Fix use-after-free in atmci_remove due to race condition</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-80556</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mmc: atmel-mci: Fix use-after-free in atmci_remove due to race condition&lt;/p&gt;
&lt;p&gt;In atmci_probe, &amp;amp;host-&amp;gt;bh_work is bound with atmci_work_func, and
atmci_interrupt, atmci_timeout_timer and atmci_dma_complete can all
queue this work on system_bh_wq.&lt;/p&gt;
&lt;p&gt;If we remove the module, atmci_remove makes cleanup and the memory
allocated for host with devm_kzalloc() is released after the remove
callback returns, while the work mentioned above may still be pending
or running. The sequence of operations that may lead to a UAF bug is
as follows:&lt;/p&gt;
&lt;p&gt;CPU0                                      CPU1&lt;/p&gt;
&lt;p&gt;| atmci_interrupt
                                          | queue_work(system_bh_wq,
                                          |            &amp;amp;host-&amp;gt;bh_work)
atmci_remove                              |
atmci_cleanup_slot(...)                   |
atmci_writel(host, ATMCI_IDR, ~0UL)       |
timer_delete_sync(&amp;amp;host-&amp;gt;timer)           |
dma_release_channel(host-&amp;gt;dma.chan)       |
free_irq(platform_get_irq(pdev, 0), host) |
                                          | atmci_work_func
                                          | // use host
// devm resources released after          |
// remove returns, host is freed          |
                                          | // use host (use-after-free)&lt;/p&gt;
&lt;p&gt;Fix it by canceling the work after all the sources that can schedule
it (IRQ handler, timeout timer and DMA com…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mmc: atmel-mci: Fix use-after-free in atmci_remove due to race condition&lt;/p&gt;
&lt;p&gt;In atmci_probe, &amp;amp;host-&amp;gt;bh_work is bound with atmci_work_func, and
atmci_interrupt, atmci_timeout_timer and atmci_dma_complete can all
queue this work on system_bh_wq.&lt;/p&gt;
&lt;p&gt;If we remove the module, atmci_remove makes cleanup and the memory
allocated for host with devm_kzalloc() is released after the remove
callback returns, while the work mentioned above may still be pending
or running. The sequence of operations that may lead to a UAF bug is
as follows:&lt;/p&gt;
&lt;p&gt;CPU0                                      CPU1&lt;/p&gt;
&lt;p&gt;| atmci_interrupt
                                          | queue_work(system_bh_wq,
                                          |            &amp;amp;host-&amp;gt;bh_work)
atmci_remove                              |
atmci_cleanup_slot(...)                   |
atmci_writel(host, ATMCI_IDR, ~0UL)       |
timer_delete_sync(&amp;amp;host-&amp;gt;timer)           |
dma_release_channel(host-&amp;gt;dma.chan)       |
free_irq(platform_get_irq(pdev, 0), host) |
                                          | atmci_work_func
                                          | // use host
// devm resources released after          |
// remove returns, host is freed          |
                                          | // use host (use-after-free)&lt;/p&gt;
&lt;p&gt;Fix it by canceling the work after all the sources that can schedule
it (IRQ handler, timeout timer and DMA com…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-80556</guid>
    </item>
  </channel>
</rss>
