<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-01T16:54:42.537928+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-46071</id>
    <title>CVE-2026-46071 — KVM: nSVM: Avoid clearing VMCB_LBR in vmcb12</title>
    <updated>2026-10-01T16:54:42.539549+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>KVM: nSVM: Avoid clearing VMCB_LBR in vmcb12</p>
<p>svm_copy_lbrs() always marks VMCB_LBR dirty in the destination VMCB.
However, nested_svm_vmexit() uses it to copy LBRs to vmcb12, and
clearing clean bits in vmcb12 is not architecturally defined.</p>
<p>Move vmcb_mark_dirty() to callers and drop it for vmcb12.</p>
<p>This also facilitates incoming refactoring that does not pass the entire
VMCB to svm_copy_lbrs().</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-46071"/>
  </entry>
</feed>
