<?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, 06 Oct 2026 05:30:54 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-21906 — wifi: iwlwifi: mvm: clean up ROC on failure</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-21906</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: iwlwifi: mvm: clean up ROC on failure&lt;/p&gt;
&lt;p&gt;If the firmware fails to start the session protection, then we
do call iwl_mvm_roc_finished() here, but that won&amp;#39;t do anything
at all because IWL_MVM_STATUS_ROC_P2P_RUNNING was never set.
Set IWL_MVM_STATUS_ROC_P2P_RUNNING in the failure/stop path.
If it started successfully before, it&amp;#39;s already set, so that
doesn&amp;#39;t matter, and if it didn&amp;#39;t start it needs to be set to
clean up.&lt;/p&gt;
&lt;p&gt;Not doing so will lead to a WARN_ON() later on a fresh remain-
on-channel, since the link is already active when activated as
it was never deactivated.&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: iwlwifi: mvm: clean up ROC on failure&lt;/p&gt;
&lt;p&gt;If the firmware fails to start the session protection, then we
do call iwl_mvm_roc_finished() here, but that won&amp;#39;t do anything
at all because IWL_MVM_STATUS_ROC_P2P_RUNNING was never set.
Set IWL_MVM_STATUS_ROC_P2P_RUNNING in the failure/stop path.
If it started successfully before, it&amp;#39;s already set, so that
doesn&amp;#39;t matter, and if it didn&amp;#39;t start it needs to be set to
clean up.&lt;/p&gt;
&lt;p&gt;Not doing so will lead to a WARN_ON() later on a fresh remain-
on-channel, since the link is already active when activated as
it was never deactivated.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-21906</guid>
    </item>
  </channel>
</rss>
