<?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>Sun, 11 Oct 2026 08:32:24 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-98338 — wifi: cfg80211: ibss: ref BSS entry for joined event</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-98338</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: ibss: ref BSS entry for joined event&lt;/p&gt;
&lt;p&gt;When the IBSS is joined, we only record the BSSID/channel in the event
and look up the BSS entry when processing it. However, that&amp;#39;s racy,
e.g. a new scan with NL80211_SCAN_FLAG_FLUSH can remove it, causing a
warning in the event work:&lt;/p&gt;
&lt;p&gt;!bss
  WARNING: net/wireless/ibss.c:37 at __cfg80211_ibss_joined+0x3d3/0x440
  Workqueue: cfg80211 cfg80211_event_work
   cfg80211_process_wdev_events+0x39f/0x5b0 net/wireless/util.c:1144
   cfg80211_process_rdev_events+0xa1/0x110 net/wireless/util.c:1179
   cfg80211_event_work+0x2f/0x40 net/wireless/core.c:393&lt;/p&gt;
&lt;p&gt;Do the lookup early (the driver is expected to only join an IBSS that
has a BSS entry) and keep a reference to it.&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: ibss: ref BSS entry for joined event&lt;/p&gt;
&lt;p&gt;When the IBSS is joined, we only record the BSSID/channel in the event
and look up the BSS entry when processing it. However, that&amp;#39;s racy,
e.g. a new scan with NL80211_SCAN_FLAG_FLUSH can remove it, causing a
warning in the event work:&lt;/p&gt;
&lt;p&gt;!bss
  WARNING: net/wireless/ibss.c:37 at __cfg80211_ibss_joined+0x3d3/0x440
  Workqueue: cfg80211 cfg80211_event_work
   cfg80211_process_wdev_events+0x39f/0x5b0 net/wireless/util.c:1144
   cfg80211_process_rdev_events+0xa1/0x110 net/wireless/util.c:1179
   cfg80211_event_work+0x2f/0x40 net/wireless/core.c:393&lt;/p&gt;
&lt;p&gt;Do the lookup early (the driver is expected to only join an IBSS that
has a BSS entry) and keep a reference to it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-98338</guid>
    </item>
  </channel>
</rss>
