<?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 20:13:48 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-41039 — firmware: cs_dsp: Fix overflow checking of wmfw header</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-41039</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;firmware: cs_dsp: Fix overflow checking of wmfw header&lt;/p&gt;
&lt;p&gt;Fix the checking that firmware file buffer is large enough for the
wmfw header, to prevent overrunning the buffer.&lt;/p&gt;
&lt;p&gt;The original code tested that the firmware data buffer contained
enough bytes for the sums of the size of the structs&lt;/p&gt;
&lt;p&gt;wmfw_header + wmfw_adsp1_sizes + wmfw_footer&lt;/p&gt;
&lt;p&gt;But wmfw_adsp1_sizes is only used on ADSP1 firmware. For ADSP2 and
Halo Core the equivalent struct is wmfw_adsp2_sizes, which is
4 bytes longer. So the length check didn&amp;#39;t guarantee that there
are enough bytes in the firmware buffer for a header with
wmfw_adsp2_sizes.&lt;/p&gt;
&lt;p&gt;This patch splits the length check into three separate parts. Each
of the wmfw_header, wmfw_adsp?_sizes and wmfw_footer are checked
separately before they are used.&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;firmware: cs_dsp: Fix overflow checking of wmfw header&lt;/p&gt;
&lt;p&gt;Fix the checking that firmware file buffer is large enough for the
wmfw header, to prevent overrunning the buffer.&lt;/p&gt;
&lt;p&gt;The original code tested that the firmware data buffer contained
enough bytes for the sums of the size of the structs&lt;/p&gt;
&lt;p&gt;wmfw_header + wmfw_adsp1_sizes + wmfw_footer&lt;/p&gt;
&lt;p&gt;But wmfw_adsp1_sizes is only used on ADSP1 firmware. For ADSP2 and
Halo Core the equivalent struct is wmfw_adsp2_sizes, which is
4 bytes longer. So the length check didn&amp;#39;t guarantee that there
are enough bytes in the firmware buffer for a header with
wmfw_adsp2_sizes.&lt;/p&gt;
&lt;p&gt;This patch splits the length check into three separate parts. Each
of the wmfw_header, wmfw_adsp?_sizes and wmfw_footer are checked
separately before they are used.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-41039</guid>
    </item>
  </channel>
</rss>
