<?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 07:35:01 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-90068 — ASoC: dapm: Fix off-by-one check on the second enum channel</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-90068</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: dapm: Fix off-by-one check on the second enum channel&lt;/p&gt;
&lt;p&gt;The snd_soc_dapm_put_enum_double() rejects item[0] once it reaches
e-&amp;gt;items, but it lets item[1] be equal to it.  Both go on to
snd_soc_enum_item_to_val(), which indexes e-&amp;gt;values with no bound of
its own, so an enum with a value table reads one element past the end.&lt;/p&gt;
&lt;p&gt;The indexing arrived with the MUX consolidation, which relaxed the
item[1] check in the same hunk.  The value MUX handler it deleted used
&amp;gt;= there, and the snd_soc_put_enum_double() in soc-ops.c still does.&lt;/p&gt;
&lt;p&gt;Only adav80x pairs a value table with two shifts, and its second
channel looks accidental, but the control does report two values.
Writing three into it reads off the end of adav80x_mux_values.  The
core catches that only under CONFIG_SND_CTL_INPUT_VALIDATION, which
defaults off.&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: dapm: Fix off-by-one check on the second enum channel&lt;/p&gt;
&lt;p&gt;The snd_soc_dapm_put_enum_double() rejects item[0] once it reaches
e-&amp;gt;items, but it lets item[1] be equal to it.  Both go on to
snd_soc_enum_item_to_val(), which indexes e-&amp;gt;values with no bound of
its own, so an enum with a value table reads one element past the end.&lt;/p&gt;
&lt;p&gt;The indexing arrived with the MUX consolidation, which relaxed the
item[1] check in the same hunk.  The value MUX handler it deleted used
&amp;gt;= there, and the snd_soc_put_enum_double() in soc-ops.c still does.&lt;/p&gt;
&lt;p&gt;Only adav80x pairs a value table with two shifts, and its second
channel looks accidental, but the control does report two values.
Writing three into it reads off the end of adav80x_mux_values.  The
core catches that only under CONFIG_SND_CTL_INPUT_VALIDATION, which
defaults off.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-90068</guid>
    </item>
  </channel>
</rss>
