<?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-10-06T11:34:04.849843+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-2025-38421</id>
    <title>CVE-2025-38421 — platform/x86/amd: pmf: Use device managed allocations</title>
    <updated>2026-10-06T11:34:04.924758+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>platform/x86/amd: pmf: Use device managed allocations</p>
<p>If setting up smart PC fails for any reason then this can lead to
a double free when unloading amd-pmf.  This is because dev-&gt;buf was
freed but never set to NULL and is again freed in amd_pmf_remove().</p>
<p>To avoid subtle allocation bugs in failures leading to a double free
change all allocations into device managed allocations.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-38421"/>
  </entry>
</feed>
