<?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-29T22:38:26.155218+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-31475</id>
    <title>CVE-2026-31475 — ASoC: sma1307: fix double free of devm_kzalloc() memory</title>
    <updated>2026-09-29T22:38:26.180323+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: sma1307: fix double free of devm_kzalloc() memory</p>
<p>A previous change added NULL checks and cleanup for allocation
failures in sma1307_setting_loaded().</p>
<p>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.</p>
<p>Drop the manual kfree() loop and let devres handle the cleanup.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-31475"/>
  </entry>
</feed>
