<?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-29T08:46:50.789272+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-2026-90068</id>
    <title>CVE-2026-90068 — ASoC: dapm: Fix off-by-one check on the second enum channel</title>
    <updated>2026-09-29T08:46:50.801224+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: dapm: Fix off-by-one check on the second enum channel</p>
<p>The snd_soc_dapm_put_enum_double() rejects item[0] once it reaches
e-&gt;items, but it lets item[1] be equal to it.  Both go on to
snd_soc_enum_item_to_val(), which indexes e-&gt;values with no bound of
its own, so an enum with a value table reads one element past the end.</p>
<p>The indexing arrived with the MUX consolidation, which relaxed the
item[1] check in the same hunk.  The value MUX handler it deleted used
&gt;= there, and the snd_soc_put_enum_double() in soc-ops.c still does.</p>
<p>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.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-90068"/>
  </entry>
</feed>
