<?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>Sun, 04 Oct 2026 18:30:37 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-50115 — KVM: nSVM: Ignore nCR3[4:0] when loading PDPTEs from memory</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-50115</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: nSVM: Ignore nCR3[4:0] when loading PDPTEs from memory&lt;/p&gt;
&lt;p&gt;Ignore nCR3[4:0] when loading PDPTEs from memory for nested SVM, as bits
4:0 of CR3 are ignored when PAE paging is used, and thus VMRUN doesn&amp;#39;t
enforce 32-byte alignment of nCR3.&lt;/p&gt;
&lt;p&gt;In the absolute worst case scenario, failure to ignore bits 4:0 can result
in an out-of-bounds read, e.g. if the target page is at the end of a
memslot, and the VMM isn&amp;#39;t using guard pages.&lt;/p&gt;
&lt;p&gt;Per the APM:&lt;/p&gt;
&lt;p&gt;The CR3 register points to the base address of the page-directory-pointer
  table. The page-directory-pointer table is aligned on a 32-byte boundary,
  with the low 5 address bits 4:0 assumed to be 0.&lt;/p&gt;
&lt;p&gt;And the SDM&amp;#39;s much more explicit:&lt;/p&gt;
&lt;p&gt;4:0    Ignored&lt;/p&gt;
&lt;p&gt;Note, KVM gets this right when loading PDPTRs, it&amp;#39;s only the nSVM flow
that is broken.&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: nSVM: Ignore nCR3[4:0] when loading PDPTEs from memory&lt;/p&gt;
&lt;p&gt;Ignore nCR3[4:0] when loading PDPTEs from memory for nested SVM, as bits
4:0 of CR3 are ignored when PAE paging is used, and thus VMRUN doesn&amp;#39;t
enforce 32-byte alignment of nCR3.&lt;/p&gt;
&lt;p&gt;In the absolute worst case scenario, failure to ignore bits 4:0 can result
in an out-of-bounds read, e.g. if the target page is at the end of a
memslot, and the VMM isn&amp;#39;t using guard pages.&lt;/p&gt;
&lt;p&gt;Per the APM:&lt;/p&gt;
&lt;p&gt;The CR3 register points to the base address of the page-directory-pointer
  table. The page-directory-pointer table is aligned on a 32-byte boundary,
  with the low 5 address bits 4:0 assumed to be 0.&lt;/p&gt;
&lt;p&gt;And the SDM&amp;#39;s much more explicit:&lt;/p&gt;
&lt;p&gt;4:0    Ignored&lt;/p&gt;
&lt;p&gt;Note, KVM gets this right when loading PDPTRs, it&amp;#39;s only the nSVM flow
that is broken.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-50115</guid>
    </item>
  </channel>
</rss>
