<?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 22:38:27 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-31475 — ASoC: sma1307: fix double free of devm_kzalloc() memory</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-31475</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: sma1307: fix double free of devm_kzalloc() memory&lt;/p&gt;
&lt;p&gt;A previous change added NULL checks and cleanup for allocation
failures in sma1307_setting_loaded().&lt;/p&gt;
&lt;p&gt;However, the cleanup for mode_set entries is wrong. Those entries are
allocated with devm_kzalloc(), so they are device-managed resources and
must not be freed with kfree(). Manually freeing them in the error path
can lead to a double free when devres later releases the same memory.&lt;/p&gt;
&lt;p&gt;Drop the manual kfree() loop and let devres handle the cleanup.&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: sma1307: fix double free of devm_kzalloc() memory&lt;/p&gt;
&lt;p&gt;A previous change added NULL checks and cleanup for allocation
failures in sma1307_setting_loaded().&lt;/p&gt;
&lt;p&gt;However, the cleanup for mode_set entries is wrong. Those entries are
allocated with devm_kzalloc(), so they are device-managed resources and
must not be freed with kfree(). Manually freeing them in the error path
can lead to a double free when devres later releases the same memory.&lt;/p&gt;
&lt;p&gt;Drop the manual kfree() loop and let devres handle the cleanup.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-31475</guid>
    </item>
  </channel>
</rss>
