<?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 12:31:46 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-72415 — ASoC: SDCA: Validate written enum value in ge_put_enum_double()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-72415</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: SDCA: Validate written enum value in ge_put_enum_double()&lt;/p&gt;
&lt;p&gt;ge_put_enum_double() passes the user-supplied enumeration index
item[0] to snd_soc_enum_item_to_val() without checking it against the
number of items in the enum:&lt;/p&gt;
&lt;p&gt;ret = snd_soc_enum_item_to_val(e, item[0]);&lt;/p&gt;
&lt;p&gt;snd_soc_enum_item_to_val() indexes the heap-allocated e-&amp;gt;values[] array
with that index (e-&amp;gt;values is set from a devm_kcalloc() of e-&amp;gt;items
entries), so a control write with an out-of-range item[0] reads past the
end of the values buffer.  The bounds check in
snd_soc_dapm_put_enum_double() only runs afterwards, so it does not
prevent the read here.&lt;/p&gt;
&lt;p&gt;Reject an out-of-range item before using it, matching the other enum put
handlers.&lt;/p&gt;
&lt;p&gt;This issue was pointed out by the Sashiko AI review bot while reviewing a
related enum-validation series:
https://lore.kernel.org/all/20260609125735.CEB651F00893@smtp.kernel.org/&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: SDCA: Validate written enum value in ge_put_enum_double()&lt;/p&gt;
&lt;p&gt;ge_put_enum_double() passes the user-supplied enumeration index
item[0] to snd_soc_enum_item_to_val() without checking it against the
number of items in the enum:&lt;/p&gt;
&lt;p&gt;ret = snd_soc_enum_item_to_val(e, item[0]);&lt;/p&gt;
&lt;p&gt;snd_soc_enum_item_to_val() indexes the heap-allocated e-&amp;gt;values[] array
with that index (e-&amp;gt;values is set from a devm_kcalloc() of e-&amp;gt;items
entries), so a control write with an out-of-range item[0] reads past the
end of the values buffer.  The bounds check in
snd_soc_dapm_put_enum_double() only runs afterwards, so it does not
prevent the read here.&lt;/p&gt;
&lt;p&gt;Reject an out-of-range item before using it, matching the other enum put
handlers.&lt;/p&gt;
&lt;p&gt;This issue was pointed out by the Sashiko AI review bot while reviewing a
related enum-validation series:
https://lore.kernel.org/all/20260609125735.CEB651F00893@smtp.kernel.org/&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-72415</guid>
    </item>
  </channel>
</rss>
