<?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, 02 Oct 2026 11:16:27 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-21909 — wifi: nl80211: reject cooked mode if it is set along with other flags</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-21909</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: nl80211: reject cooked mode if it is set along with other flags&lt;/p&gt;
&lt;p&gt;It is possible to set both MONITOR_FLAG_COOK_FRAMES and MONITOR_FLAG_ACTIVE
flags simultaneously on the same monitor interface from the userspace. This
causes a sub-interface to be created with no IEEE80211_SDATA_IN_DRIVER bit
set because the monitor interface is in the cooked state and it takes
precedence over all other states. When the interface is then being deleted
the kernel calls WARN_ONCE() from check_sdata_in_driver() because of missing
that bit.&lt;/p&gt;
&lt;p&gt;Fix this by rejecting MONITOR_FLAG_COOK_FRAMES if it is set along with
other flags.&lt;/p&gt;
&lt;p&gt;Found by Linux Verification Center (linuxtesting.org) with Syzkaller.&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: nl80211: reject cooked mode if it is set along with other flags&lt;/p&gt;
&lt;p&gt;It is possible to set both MONITOR_FLAG_COOK_FRAMES and MONITOR_FLAG_ACTIVE
flags simultaneously on the same monitor interface from the userspace. This
causes a sub-interface to be created with no IEEE80211_SDATA_IN_DRIVER bit
set because the monitor interface is in the cooked state and it takes
precedence over all other states. When the interface is then being deleted
the kernel calls WARN_ONCE() from check_sdata_in_driver() because of missing
that bit.&lt;/p&gt;
&lt;p&gt;Fix this by rejecting MONITOR_FLAG_COOK_FRAMES if it is set along with
other flags.&lt;/p&gt;
&lt;p&gt;Found by Linux Verification Center (linuxtesting.org) with Syzkaller.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-21909</guid>
    </item>
  </channel>
</rss>
