<?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>Tue, 29 Sep 2026 06:55:28 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-72300 — ASoC: SOF: topology: validate vendor array size before parsing</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-72300</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: topology: validate vendor array size before parsing&lt;/p&gt;
&lt;p&gt;sof_parse_token_sets() reads array-&amp;gt;size while iterating over topology
private data. The loop condition only checks that some data remains, so a
malformed topology with a truncated trailing vendor array can make the
parser read the size field before a full vendor-array header is available.&lt;/p&gt;
&lt;p&gt;Validate that the remaining private data contains a complete
snd_soc_tplg_vendor_array header before reading array-&amp;gt;size.&lt;/p&gt;
&lt;p&gt;The declared array size check also needs to remain signed. asize is an int,
but sizeof(*array) has type size_t, so comparing them directly promotes
negative asize values to unsigned and lets them pass the check,
as reported in the stable review thread reference below.&lt;/p&gt;
&lt;p&gt;Cast sizeof(*array) to int when validating the declared array size. This
rejects negative, zero and otherwise too-small sizes before the parser
dispatches to the tuple-specific code.&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: topology: validate vendor array size before parsing&lt;/p&gt;
&lt;p&gt;sof_parse_token_sets() reads array-&amp;gt;size while iterating over topology
private data. The loop condition only checks that some data remains, so a
malformed topology with a truncated trailing vendor array can make the
parser read the size field before a full vendor-array header is available.&lt;/p&gt;
&lt;p&gt;Validate that the remaining private data contains a complete
snd_soc_tplg_vendor_array header before reading array-&amp;gt;size.&lt;/p&gt;
&lt;p&gt;The declared array size check also needs to remain signed. asize is an int,
but sizeof(*array) has type size_t, so comparing them directly promotes
negative asize values to unsigned and lets them pass the check,
as reported in the stable review thread reference below.&lt;/p&gt;
&lt;p&gt;Cast sizeof(*array) to int when validating the declared array size. This
rejects negative, zero and otherwise too-small sizes before the parser
dispatches to the tuple-specific code.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-72300</guid>
    </item>
  </channel>
</rss>
