<?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 10:30:26 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23281 — wifi: libertas: fix use-after-free in lbs_free_adapter()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-23281</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;wifi: libertas: fix use-after-free in lbs_free_adapter()&lt;/p&gt;
&lt;p&gt;The lbs_free_adapter() function uses timer_delete() (non-synchronous)
for both command_timer and tx_lockup_timer before the structure is
freed. This is incorrect because timer_delete() does not wait for
any running timer callback to complete.&lt;/p&gt;
&lt;p&gt;If a timer callback is executing when lbs_free_adapter() is called,
the callback will access freed memory since lbs_cfg_free() frees the
containing structure immediately after lbs_free_adapter() returns.&lt;/p&gt;
&lt;p&gt;Both timer callbacks (lbs_cmd_timeout_handler and lbs_tx_lockup_handler)
access priv-&amp;gt;driver_lock, priv-&amp;gt;cur_cmd, priv-&amp;gt;dev, and other fields,
which would all be use-after-free violations.&lt;/p&gt;
&lt;p&gt;Use timer_delete_sync() instead to ensure any running timer callback
has completed before returning.&lt;/p&gt;
&lt;p&gt;This bug was introduced in commit 8f641d93c38a (&amp;#34;libertas: detect TX
lockups and reset hardware&amp;#34;) where del_timer() was used instead of
del_timer_sync() in the cleanup path. The command_timer has had the
same issue since the driver was first written.&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;wifi: libertas: fix use-after-free in lbs_free_adapter()&lt;/p&gt;
&lt;p&gt;The lbs_free_adapter() function uses timer_delete() (non-synchronous)
for both command_timer and tx_lockup_timer before the structure is
freed. This is incorrect because timer_delete() does not wait for
any running timer callback to complete.&lt;/p&gt;
&lt;p&gt;If a timer callback is executing when lbs_free_adapter() is called,
the callback will access freed memory since lbs_cfg_free() frees the
containing structure immediately after lbs_free_adapter() returns.&lt;/p&gt;
&lt;p&gt;Both timer callbacks (lbs_cmd_timeout_handler and lbs_tx_lockup_handler)
access priv-&amp;gt;driver_lock, priv-&amp;gt;cur_cmd, priv-&amp;gt;dev, and other fields,
which would all be use-after-free violations.&lt;/p&gt;
&lt;p&gt;Use timer_delete_sync() instead to ensure any running timer callback
has completed before returning.&lt;/p&gt;
&lt;p&gt;This bug was introduced in commit 8f641d93c38a (&amp;#34;libertas: detect TX
lockups and reset hardware&amp;#34;) where del_timer() was used instead of
del_timer_sync() in the cleanup path. The command_timer has had the
same issue since the driver was first written.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-23281</guid>
    </item>
  </channel>
</rss>
