<?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 07:24:31 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80944 — wifi: mwifiex: Detach sync cmd buffer on interrupted wait</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-80944</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: mwifiex: Detach sync cmd buffer on interrupted wait&lt;/p&gt;
&lt;p&gt;mwifiex synchronous commands keep the caller-provided data buffer in
cmd_node-&amp;gt;data_buf. Several callers pass stack-allocated objects there.&lt;/p&gt;
&lt;p&gt;If wait_event_interruptible_timeout() is interrupted, the caller can
return and release that stack object while the firmware command is still
the current command. A late firmware response then reaches the normal
response handler, which can copy data through cmd_node-&amp;gt;data_buf into the
stale stack address.&lt;/p&gt;
&lt;p&gt;This fixes a stack corruption observed during repeated association and
disassociation cycles. The panic trace showed the command wait being
interrupted immediately before a bad pointer dereference:&lt;/p&gt;
&lt;p&gt;cmd_wait_q terminated: -512
  Unable to handle kernel paging request at virtual address 002c583837384662
  Kernel panic - not syncing: stack-protector: Kernel stack is corrupted
  ...
  Tainted: [M]=MACHINE_CHECK&lt;/p&gt;
&lt;p&gt;The fault address decodes as little-endian ASCII:&lt;/p&gt;
&lt;p&gt;0x002c583837384662 -&amp;gt; &amp;#34;bF878X,\0&amp;#34;&lt;/p&gt;
&lt;p&gt;which is a fragment of the VERSION_EXT firmware string exposed as
debugfs &amp;#34;verext&amp;#34;:&lt;/p&gt;
&lt;p&gt;w8997o-V4, RF878X, FP92, 16.92.21.p153.7&lt;/p&gt;
&lt;p&gt;The same runs also showed corrupted control data containing:&lt;/p&gt;
&lt;p&gt;0x2400372e333531 -&amp;gt; &amp;#34;153.7\0$&amp;#34;&lt;/p&gt;
&lt;p&gt;which is the tail of the same VERSION_EXT string. This points at a late
VERSION_EXT response writing through a stale stack-backed data_buf after
the interrupted wait returned.&lt;/p&gt;
&lt;p&gt;After cancelling…&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: mwifiex: Detach sync cmd buffer on interrupted wait&lt;/p&gt;
&lt;p&gt;mwifiex synchronous commands keep the caller-provided data buffer in
cmd_node-&amp;gt;data_buf. Several callers pass stack-allocated objects there.&lt;/p&gt;
&lt;p&gt;If wait_event_interruptible_timeout() is interrupted, the caller can
return and release that stack object while the firmware command is still
the current command. A late firmware response then reaches the normal
response handler, which can copy data through cmd_node-&amp;gt;data_buf into the
stale stack address.&lt;/p&gt;
&lt;p&gt;This fixes a stack corruption observed during repeated association and
disassociation cycles. The panic trace showed the command wait being
interrupted immediately before a bad pointer dereference:&lt;/p&gt;
&lt;p&gt;cmd_wait_q terminated: -512
  Unable to handle kernel paging request at virtual address 002c583837384662
  Kernel panic - not syncing: stack-protector: Kernel stack is corrupted
  ...
  Tainted: [M]=MACHINE_CHECK&lt;/p&gt;
&lt;p&gt;The fault address decodes as little-endian ASCII:&lt;/p&gt;
&lt;p&gt;0x002c583837384662 -&amp;gt; &amp;#34;bF878X,\0&amp;#34;&lt;/p&gt;
&lt;p&gt;which is a fragment of the VERSION_EXT firmware string exposed as
debugfs &amp;#34;verext&amp;#34;:&lt;/p&gt;
&lt;p&gt;w8997o-V4, RF878X, FP92, 16.92.21.p153.7&lt;/p&gt;
&lt;p&gt;The same runs also showed corrupted control data containing:&lt;/p&gt;
&lt;p&gt;0x2400372e333531 -&amp;gt; &amp;#34;153.7\0$&amp;#34;&lt;/p&gt;
&lt;p&gt;which is the tail of the same VERSION_EXT string. This points at a late
VERSION_EXT response writing through a stale stack-backed data_buf after
the interrupted wait returned.&lt;/p&gt;
&lt;p&gt;After cancelling…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-80944</guid>
    </item>
  </channel>
</rss>
