https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 22:04:53 +0000 https://vulnerability.circl.lu/vuln/cve-2026-43133 <p><strong>Affected:</strong> Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 9, Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 8, Red Hat OpenShift Container Platform 4</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation</p> <p>Commit cc3ed80ae69f (&#34;KVM: nSVM: always use vmcb01 to for vmsave/vmload of guest state&#34;) made KVM always use vmcb01 for the fields controlled by VMSAVE/VMLOAD, but it missed updating the VMLOAD/VMSAVE emulation code to always use vmcb01.</p> <p>As a result, if VMSAVE/VMLOAD is executed by an L2 guest and is not intercepted by L1, KVM will mistakenly use vmcb02. Always use vmcb01 instead of the current VMCB.</p> <p><strong>Affected:</strong> Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 9, Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 8, Red Hat OpenShift Container Platform 4</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation</p> <p>Commit cc3ed80ae69f (&#34;KVM: nSVM: always use vmcb01 to for vmsave/vmload of guest state&#34;) made KVM always use vmcb01 for the fields controlled by VMSAVE/VMLOAD, but it missed updating the VMLOAD/VMSAVE emulation code to always use vmcb01.</p> <p>As a result, if VMSAVE/VMLOAD is executed by an L2 guest and is not intercepted by L1, KVM will mistakenly use vmcb02. Always use vmcb01 instead of the current VMCB.</p> https://vulnerability.circl.lu/vuln/cve-2026-43133