<?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>Thu, 01 Oct 2026 13:56:28 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-46014 — KVM: SVM: Add missing save/restore handling of LBR MSRs</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-46014</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: SVM: Add missing save/restore handling of LBR MSRs&lt;/p&gt;
&lt;p&gt;MSR_IA32_DEBUGCTLMSR and LBR MSRs are currently not enumerated by
KVM_GET_MSR_INDEX_LIST, and LBR MSRs cannot be set with KVM_SET_MSRS. So
save/restore is completely broken.&lt;/p&gt;
&lt;p&gt;Fix it by adding the MSRs to msrs_to_save_base, and allowing writes to
LBR MSRs from userspace only (as they are read-only MSRs) if LBR
virtualization is enabled.  Additionally, to correctly restore L1&amp;#39;s LBRs
while L2 is running, make sure the LBRs are copied from the captured
VMCB01 save area in svm_copy_vmrun_state().&lt;/p&gt;
&lt;p&gt;Note, for VMX, this also fixes a flaw where MSR_IA32_DEBUGCTLMSR isn&amp;#39;t
reported as an MSR to save/restore.&lt;/p&gt;
&lt;p&gt;Note #2, over-reporting MSR_IA32_LASTxxx on Intel is ok, as KVM already
handles unsupported reads and writes thanks to commit b5e2fec0ebc3 (&amp;#34;KVM:
Ignore DEBUGCTL MSRs with no effect&amp;#34;) (kvm_do_msr_access() will morph the
unsupported userspace write into a nop).&lt;/p&gt;
&lt;p&gt;[sean: guard with lbrv checks, massage changelog]&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: SVM: Add missing save/restore handling of LBR MSRs&lt;/p&gt;
&lt;p&gt;MSR_IA32_DEBUGCTLMSR and LBR MSRs are currently not enumerated by
KVM_GET_MSR_INDEX_LIST, and LBR MSRs cannot be set with KVM_SET_MSRS. So
save/restore is completely broken.&lt;/p&gt;
&lt;p&gt;Fix it by adding the MSRs to msrs_to_save_base, and allowing writes to
LBR MSRs from userspace only (as they are read-only MSRs) if LBR
virtualization is enabled.  Additionally, to correctly restore L1&amp;#39;s LBRs
while L2 is running, make sure the LBRs are copied from the captured
VMCB01 save area in svm_copy_vmrun_state().&lt;/p&gt;
&lt;p&gt;Note, for VMX, this also fixes a flaw where MSR_IA32_DEBUGCTLMSR isn&amp;#39;t
reported as an MSR to save/restore.&lt;/p&gt;
&lt;p&gt;Note #2, over-reporting MSR_IA32_LASTxxx on Intel is ok, as KVM already
handles unsupported reads and writes thanks to commit b5e2fec0ebc3 (&amp;#34;KVM:
Ignore DEBUGCTL MSRs with no effect&amp;#34;) (kvm_do_msr_access() will morph the
unsupported userspace write into a nop).&lt;/p&gt;
&lt;p&gt;[sean: guard with lbrv checks, massage changelog]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-46014</guid>
    </item>
  </channel>
</rss>
