<?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:49 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-68197 — wifi: mwifiex: fix NULL dereference when the AP has HT-cap but no HT-oper</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-68197</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: fix NULL dereference when the AP has HT-cap but no HT-oper&lt;/p&gt;
&lt;p&gt;mwifiex_tdls_add_ht_oper() gates its follow-the-AP-bandwidth path on
bss_desc-&amp;gt;bcn_ht_cap being present, but then dereferences a different
pointer, bss_desc-&amp;gt;bcn_ht_oper:&lt;/p&gt;
&lt;p&gt;if (ISSUPP_CHANWIDTH40(priv-&amp;gt;adapter-&amp;gt;hw_dot_11n_dev_cap) &amp;amp;&amp;amp;
	    bss_desc-&amp;gt;bcn_ht_cap &amp;amp;&amp;amp;
	    ISALLOWED_CHANWIDTH40(bss_desc-&amp;gt;bcn_ht_oper-&amp;gt;ht_param))&lt;/p&gt;
&lt;p&gt;bcn_ht_cap and bcn_ht_oper are populated independently while parsing the
associated AP&amp;#39;s beacon in mwifiex_update_bss_desc_with_ie(): an AP that
advertises an HT Capabilities element but no HT Operation element leaves
bcn_ht_cap non-NULL and bcn_ht_oper NULL. Setting up a TDLS link to a
peer while associated to such an AP then dereferences the NULL
bcn_ht_oper and crashes the kernel. Every other bcn_ht_oper user in the
driver NULL-checks it first.&lt;/p&gt;
&lt;p&gt;Guard on the pointer that is actually dereferenced.&lt;/p&gt;
&lt;p&gt;Found by 0sec automated security-research tooling (https://0sec.ai).&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: fix NULL dereference when the AP has HT-cap but no HT-oper&lt;/p&gt;
&lt;p&gt;mwifiex_tdls_add_ht_oper() gates its follow-the-AP-bandwidth path on
bss_desc-&amp;gt;bcn_ht_cap being present, but then dereferences a different
pointer, bss_desc-&amp;gt;bcn_ht_oper:&lt;/p&gt;
&lt;p&gt;if (ISSUPP_CHANWIDTH40(priv-&amp;gt;adapter-&amp;gt;hw_dot_11n_dev_cap) &amp;amp;&amp;amp;
	    bss_desc-&amp;gt;bcn_ht_cap &amp;amp;&amp;amp;
	    ISALLOWED_CHANWIDTH40(bss_desc-&amp;gt;bcn_ht_oper-&amp;gt;ht_param))&lt;/p&gt;
&lt;p&gt;bcn_ht_cap and bcn_ht_oper are populated independently while parsing the
associated AP&amp;#39;s beacon in mwifiex_update_bss_desc_with_ie(): an AP that
advertises an HT Capabilities element but no HT Operation element leaves
bcn_ht_cap non-NULL and bcn_ht_oper NULL. Setting up a TDLS link to a
peer while associated to such an AP then dereferences the NULL
bcn_ht_oper and crashes the kernel. Every other bcn_ht_oper user in the
driver NULL-checks it first.&lt;/p&gt;
&lt;p&gt;Guard on the pointer that is actually dereferenced.&lt;/p&gt;
&lt;p&gt;Found by 0sec automated security-research tooling (https://0sec.ai).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-68197</guid>
    </item>
  </channel>
</rss>
