<?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 21:30:34 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-48793 — KVM: x86: nSVM: fix potential NULL derefernce on nested migration</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-48793</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;KVM: x86: nSVM: fix potential NULL derefernce on nested migration&lt;/p&gt;
&lt;p&gt;Turns out that due to review feedback and/or rebases
I accidentally moved the call to nested_svm_load_cr3 to be too early,
before the NPT is enabled, which is very wrong to do.&lt;/p&gt;
&lt;p&gt;KVM can&amp;#39;t even access guest memory at that point as nested NPT
is needed for that, and of course it won&amp;#39;t initialize the walk_mmu,
which is main issue the patch was addressing.&lt;/p&gt;
&lt;p&gt;Fix this for real.&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;KVM: x86: nSVM: fix potential NULL derefernce on nested migration&lt;/p&gt;
&lt;p&gt;Turns out that due to review feedback and/or rebases
I accidentally moved the call to nested_svm_load_cr3 to be too early,
before the NPT is enabled, which is very wrong to do.&lt;/p&gt;
&lt;p&gt;KVM can&amp;#39;t even access guest memory at that point as nested NPT
is needed for that, and of course it won&amp;#39;t initialize the walk_mmu,
which is main issue the patch was addressing.&lt;/p&gt;
&lt;p&gt;Fix this for real.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-48793</guid>
    </item>
  </channel>
</rss>
