<?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>Sat, 03 Oct 2026 04:08:45 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-57805 — ASoC: SOF: Intel: hda-dai: Do not release the link DMA on STOP</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-57805</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;ASoC: SOF: Intel: hda-dai: Do not release the link DMA on STOP&lt;/p&gt;
&lt;p&gt;The linkDMA should not be released on stop trigger since a stream re-start
might happen without closing of the stream. This leaves a short time for
other streams to &amp;#39;steal&amp;#39; the linkDMA since it has been released.&lt;/p&gt;
&lt;p&gt;This issue is not easy to reproduce under normal conditions as usually
after stop the stream is closed, or the same stream is restarted, but if
another stream got in between the stop and start, like this:
aplay -Dhw:0,3 -c2 -r48000 -fS32_LE /dev/zero -d 120
CTRL+z
aplay -Dhw:0,0 -c2 -r48000 -fS32_LE /dev/zero -d 120&lt;/p&gt;
&lt;p&gt;then the link DMA channels will be mixed up, resulting firmware error or
crash.&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;ASoC: SOF: Intel: hda-dai: Do not release the link DMA on STOP&lt;/p&gt;
&lt;p&gt;The linkDMA should not be released on stop trigger since a stream re-start
might happen without closing of the stream. This leaves a short time for
other streams to &amp;#39;steal&amp;#39; the linkDMA since it has been released.&lt;/p&gt;
&lt;p&gt;This issue is not easy to reproduce under normal conditions as usually
after stop the stream is closed, or the same stream is restarted, but if
another stream got in between the stop and start, like this:
aplay -Dhw:0,3 -c2 -r48000 -fS32_LE /dev/zero -d 120
CTRL+z
aplay -Dhw:0,0 -c2 -r48000 -fS32_LE /dev/zero -d 120&lt;/p&gt;
&lt;p&gt;then the link DMA channels will be mixed up, resulting firmware error or
crash.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-57805</guid>
    </item>
  </channel>
</rss>
