<?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 10:47:42 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23185 — wifi: iwlwifi: mld: cancel mlo_scan_start_wk</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-23185</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: iwlwifi: mld: cancel mlo_scan_start_wk&lt;/p&gt;
&lt;p&gt;mlo_scan_start_wk is not canceled on disconnection. In fact, it is not
canceled anywhere except in the restart cleanup, where we don&amp;#39;t really
have to.&lt;/p&gt;
&lt;p&gt;This can cause an init-after-queue issue: if, for example, the work was
queued and then drv_change_interface got executed.&lt;/p&gt;
&lt;p&gt;This can also cause use-after-free: if the work is executed after the
vif is freed.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: iwlwifi: mld: cancel mlo_scan_start_wk&lt;/p&gt;
&lt;p&gt;mlo_scan_start_wk is not canceled on disconnection. In fact, it is not
canceled anywhere except in the restart cleanup, where we don&amp;#39;t really
have to.&lt;/p&gt;
&lt;p&gt;This can cause an init-after-queue issue: if, for example, the work was
queued and then drv_change_interface got executed.&lt;/p&gt;
&lt;p&gt;This can also cause use-after-free: if the work is executed after the
vif is freed.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-23185</guid>
    </item>
  </channel>
</rss>
