<?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>Mon, 28 Sep 2026 19:50:57 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-97600 — ieee802154: cc2520: fix FIFOP work use-after-free</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-97600</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;ieee802154: cc2520: fix FIFOP work use-after-free&lt;/p&gt;
&lt;p&gt;The FIFOP interrupt handler queues cc2520_fifop_irqwork.  On removal,
cc2520_remove() only flushes the work.  The devm-managed FIFOP IRQ
remains active until after -&amp;gt;remove() returns and can queue the work
again after that flush, allowing it to run after the private data is
released.&lt;/p&gt;
&lt;p&gt;Disable the work with disable_work_sync() instead of flushing it, so
the handler can no longer queue it once removal begins.  Destroy the
buffer mutex last, since the worker and the stop callback invoked
through ieee802154_unregister_hw() both take it.&lt;/p&gt;
&lt;p&gt;Found by an in-house static analysis tool.&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;ieee802154: cc2520: fix FIFOP work use-after-free&lt;/p&gt;
&lt;p&gt;The FIFOP interrupt handler queues cc2520_fifop_irqwork.  On removal,
cc2520_remove() only flushes the work.  The devm-managed FIFOP IRQ
remains active until after -&amp;gt;remove() returns and can queue the work
again after that flush, allowing it to run after the private data is
released.&lt;/p&gt;
&lt;p&gt;Disable the work with disable_work_sync() instead of flushing it, so
the handler can no longer queue it once removal begins.  Destroy the
buffer mutex last, since the worker and the stop callback invoked
through ieee802154_unregister_hw() both take it.&lt;/p&gt;
&lt;p&gt;Found by an in-house static analysis tool.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-97600</guid>
    </item>
  </channel>
</rss>
