<?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://db.gcve.eu</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>Fri, 20 Nov 2026 21:21:22 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99711 — KVM: nVMX: Process each host MSR entry at most once when unwinding failed VM-Entry</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99711</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: nVMX: Process each host MSR entry at most once when unwinding failed VM-Entry&lt;/p&gt;
&lt;p&gt;Add a missing &amp;#34;break&amp;#34; in the inner for-loop of the open coded mess that
unwinds MSRs back to the pre-VM-Enter state when VMLAUNCH/VMRESUME VM-Fails
due to a consistency check that is caught by hardware but missed by KVM.
I.e. move on to the next MSR in the VM-Entry load list after performing a
write using a value found in the VM-Exit load list.  Processing *every*
matching entry in the VM-Exit load list makes the processing quadratic,
which is problematic if the load lists are full of MSRs that are expensive
to emulate.  E.g. writing APIC_BASE triggers kvm_recalculate_apic_map() and
a whole pile of unnecessary work.&lt;/p&gt;
&lt;p&gt;Functionally, arbitrarily restoring the value of the first matching entry
is &amp;#34;fine&amp;#34;, because none of this is architecturally correct: the load lists
are never supposed to have been used in the first place.  In practice, it&amp;#39;s
likely a moot point as no well-behaved VMM will have multiple, diverging
entries in the load lists.&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: nVMX: Process each host MSR entry at most once when unwinding failed VM-Entry&lt;/p&gt;
&lt;p&gt;Add a missing &amp;#34;break&amp;#34; in the inner for-loop of the open coded mess that
unwinds MSRs back to the pre-VM-Enter state when VMLAUNCH/VMRESUME VM-Fails
due to a consistency check that is caught by hardware but missed by KVM.
I.e. move on to the next MSR in the VM-Entry load list after performing a
write using a value found in the VM-Exit load list.  Processing *every*
matching entry in the VM-Exit load list makes the processing quadratic,
which is problematic if the load lists are full of MSRs that are expensive
to emulate.  E.g. writing APIC_BASE triggers kvm_recalculate_apic_map() and
a whole pile of unnecessary work.&lt;/p&gt;
&lt;p&gt;Functionally, arbitrarily restoring the value of the first matching entry
is &amp;#34;fine&amp;#34;, because none of this is architecturally correct: the load lists
are never supposed to have been used in the first place.  In practice, it&amp;#39;s
likely a moot point as no well-behaved VMM will have multiple, diverging
entries in the load lists.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99711</guid>
    </item>
  </channel>
</rss>
