<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T16:39:59.845914+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2024-41039</id>
    <title>CVE-2024-41039 — firmware: cs_dsp: Fix overflow checking of wmfw header</title>
    <updated>2026-09-30T16:39:59.862151+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>firmware: cs_dsp: Fix overflow checking of wmfw header</p>
<p>Fix the checking that firmware file buffer is large enough for the
wmfw header, to prevent overrunning the buffer.</p>
<p>The original code tested that the firmware data buffer contained
enough bytes for the sums of the size of the structs</p>
<p>wmfw_header + wmfw_adsp1_sizes + wmfw_footer</p>
<p>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't guarantee that there
are enough bytes in the firmware buffer for a header with
wmfw_adsp2_sizes.</p>
<p>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.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2024-41039"/>
  </entry>
</feed>
