<?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-29T03:51:04.989654+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-37996</id>
    <title>CVE-2025-37996 — KVM: arm64: Fix uninitialized memcache pointer in user_mem_abort()</title>
    <updated>2026-09-29T03:51:05.005867+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>KVM: arm64: Fix uninitialized memcache pointer in user_mem_abort()</p>
<p>Commit fce886a60207 ("KVM: arm64: Plumb the pKVM MMU in KVM") made the
initialization of the local memcache variable in user_mem_abort()
conditional, leaving a codepath where it is used uninitialized via
kvm_pgtable_stage2_map().</p>
<p>This can fail on any path that requires a stage-2 allocation
without transition via a permission fault or dirty logging.</p>
<p>Fix this by making sure that memcache is always valid.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-37996"/>
  </entry>
</feed>
