<?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>Thu, 01 Oct 2026 23:43:26 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53589 — wifi: iwlwifi: mvm: don't trust firmware n_channels</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53589</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: don&amp;#39;t trust firmware n_channels&lt;/p&gt;
&lt;p&gt;If the firmware sends us a corrupted MCC response with
n_channels much larger than the command response can be,
we might copy far too much (uninitialized) memory and
even crash if the n_channels is large enough to make it
run out of the one page allocated for the FW response.&lt;/p&gt;
&lt;p&gt;Fix that by checking the lengths. Doing a &amp;lt; comparison
would be sufficient, but the firmware should be doing
it correctly, so check more strictly.&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: don&amp;#39;t trust firmware n_channels&lt;/p&gt;
&lt;p&gt;If the firmware sends us a corrupted MCC response with
n_channels much larger than the command response can be,
we might copy far too much (uninitialized) memory and
even crash if the n_channels is large enough to make it
run out of the one page allocated for the FW response.&lt;/p&gt;
&lt;p&gt;Fix that by checking the lengths. Doing a &amp;lt; comparison
would be sufficient, but the firmware should be doing
it correctly, so check more strictly.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-53589</guid>
    </item>
  </channel>
</rss>
