<?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>Fri, 09 Oct 2026 15:31:49 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-98339 — wifi: cfg80211: don't filter by BSS type when removing stale entries</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-98339</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: cfg80211: don&amp;#39;t filter by BSS type when removing stale entries&lt;/p&gt;
&lt;p&gt;When an assoc AP switches to a channel that already has a BSS entry,
cfg80211_update_assoc_bss_entry() removes that entry before rehashing
the real one, since the two would otherwise collide in the BSS rbtree.&lt;/p&gt;
&lt;p&gt;The lookup for that entry also required it to match the connection&amp;#39;s BSS
type, so an entry advertising e.g. the IBSS capability bit was left in
place, and the following cfg80211_rehash_bss() then ran into it:&lt;/p&gt;
&lt;p&gt;WARN_ON(!cmp)&lt;/p&gt;
&lt;p&gt;Changing the type shouldn&amp;#39;t really happen, but can be triggered by a
rogue AP/device, so drop the check and remove any entries matching
the comparison.&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: cfg80211: don&amp;#39;t filter by BSS type when removing stale entries&lt;/p&gt;
&lt;p&gt;When an assoc AP switches to a channel that already has a BSS entry,
cfg80211_update_assoc_bss_entry() removes that entry before rehashing
the real one, since the two would otherwise collide in the BSS rbtree.&lt;/p&gt;
&lt;p&gt;The lookup for that entry also required it to match the connection&amp;#39;s BSS
type, so an entry advertising e.g. the IBSS capability bit was left in
place, and the following cfg80211_rehash_bss() then ran into it:&lt;/p&gt;
&lt;p&gt;WARN_ON(!cmp)&lt;/p&gt;
&lt;p&gt;Changing the type shouldn&amp;#39;t really happen, but can be triggered by a
rogue AP/device, so drop the check and remove any entries matching
the comparison.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-98339</guid>
    </item>
  </channel>
</rss>
