<?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-29T02:58:01.912682+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-2022-50115</id>
    <title>CVE-2022-50115 — ASoC: SOF: ipc3-topology: Prevent double freeing of ipc_control_data via load_bytes</title>
    <updated>2026-09-29T02:58:01.975315+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>ASoC: SOF: ipc3-topology: Prevent double freeing of ipc_control_data via load_bytes</p>
<p>We have sanity checks for byte controls and if any of the fail the locally
allocated scontrol-&gt;ipc_control_data is freed up, but not set to NULL.</p>
<p>On a rollback path of the error the higher level code will also try to free
the scontrol-&gt;ipc_control_data which will eventually going to lead to
memory corruption as double freeing memory is not a good thing.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2022-50115"/>
  </entry>
</feed>
