<?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>Wed, 30 Sep 2026 01:09:37 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-72262 — ASoC: SOF: ipc3-control: Fix heap overflow in bytes_ext put/get</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-72262</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: ipc3-control: Fix heap overflow in bytes_ext put/get&lt;/p&gt;
&lt;p&gt;The ipc_control_data buffer is allocated as kzalloc(max_size), where
max_size covers the entire struct sof_ipc_ctrl_data including its
flexible array payload. However, the bounds checks in bytes_ext_put
and _bytes_ext_get compared user data lengths against max_size
directly, ignoring that cdata-&amp;gt;data sits at an offset of
sizeof(struct sof_ipc_ctrl_data) bytes into the allocation.&lt;/p&gt;
&lt;p&gt;This allowed writing up to sizeof(struct sof_ipc_ctrl_data) bytes past
the end of the heap buffer from unprivileged userspace via the ALSA TLV
kcontrol interface, and similarly allowed over-reading adjacent heap
data on the get path.&lt;/p&gt;
&lt;p&gt;Fix all bounds checks to subtract sizeof(*cdata) from max_size so they
reflect the actual space available at the cdata-&amp;gt;data offset. Also fix
the error-path restore in bytes_ext_put which wrote to cdata-&amp;gt;data
instead of cdata, causing the same overflow.&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: ipc3-control: Fix heap overflow in bytes_ext put/get&lt;/p&gt;
&lt;p&gt;The ipc_control_data buffer is allocated as kzalloc(max_size), where
max_size covers the entire struct sof_ipc_ctrl_data including its
flexible array payload. However, the bounds checks in bytes_ext_put
and _bytes_ext_get compared user data lengths against max_size
directly, ignoring that cdata-&amp;gt;data sits at an offset of
sizeof(struct sof_ipc_ctrl_data) bytes into the allocation.&lt;/p&gt;
&lt;p&gt;This allowed writing up to sizeof(struct sof_ipc_ctrl_data) bytes past
the end of the heap buffer from unprivileged userspace via the ALSA TLV
kcontrol interface, and similarly allowed over-reading adjacent heap
data on the get path.&lt;/p&gt;
&lt;p&gt;Fix all bounds checks to subtract sizeof(*cdata) from max_size so they
reflect the actual space available at the cdata-&amp;gt;data offset. Also fix
the error-path restore in bytes_ext_put which wrote to cdata-&amp;gt;data
instead of cdata, causing the same overflow.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-72262</guid>
    </item>
  </channel>
</rss>
