<?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>Sat, 03 Oct 2026 20:53:53 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-46032 — KVM: nSVM: Triple fault if restore host CR3 fails on nested #VMEXIT</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-46032</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: Triple fault if restore host CR3 fails on nested #VMEXIT&lt;/p&gt;
&lt;p&gt;If loading L1&amp;#39;s CR3 fails on a nested #VMEXIT, nested_svm_vmexit()
returns an error code that is ignored by most callers, and continues to
run L1 with corrupted state. A sane recovery is not possible in this
case, and HW behavior is to cause a shutdown. Inject a triple fault
instead, and do not return early from nested_svm_vmexit(). Continue
cleaning up the vCPU state (e.g. clear pending exceptions), to handle
the failure as gracefully as possible.&lt;/p&gt;
&lt;p&gt;From the APM:&lt;/p&gt;
&lt;p&gt;Upon #VMEXIT, the processor performs the following actions in order to
  return to the host execution context:&lt;/p&gt;
&lt;p&gt;...&lt;/p&gt;
&lt;p&gt;if (illegal host state loaded, or exception while loading host state)
      shutdown
  else
      execute first host instruction following the VMRUN&lt;/p&gt;
&lt;p&gt;Remove the return value of nested_svm_vmexit(), which is mostly
unchecked anyway.&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: Triple fault if restore host CR3 fails on nested #VMEXIT&lt;/p&gt;
&lt;p&gt;If loading L1&amp;#39;s CR3 fails on a nested #VMEXIT, nested_svm_vmexit()
returns an error code that is ignored by most callers, and continues to
run L1 with corrupted state. A sane recovery is not possible in this
case, and HW behavior is to cause a shutdown. Inject a triple fault
instead, and do not return early from nested_svm_vmexit(). Continue
cleaning up the vCPU state (e.g. clear pending exceptions), to handle
the failure as gracefully as possible.&lt;/p&gt;
&lt;p&gt;From the APM:&lt;/p&gt;
&lt;p&gt;Upon #VMEXIT, the processor performs the following actions in order to
  return to the host execution context:&lt;/p&gt;
&lt;p&gt;...&lt;/p&gt;
&lt;p&gt;if (illegal host state loaded, or exception while loading host state)
      shutdown
  else
      execute first host instruction following the VMRUN&lt;/p&gt;
&lt;p&gt;Remove the return value of nested_svm_vmexit(), which is mostly
unchecked anyway.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-46032</guid>
    </item>
  </channel>
</rss>
