CVE-2026-43133

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation<br /> <br /> Commit cc3ed80ae69f ("KVM: nSVM: always use vmcb01 to for vmsave/vmload<br /> of guest state") made KVM always use vmcb01 for the fields controlled by<br /> VMSAVE/VMLOAD, but it missed updating the VMLOAD/VMSAVE emulation code<br /> to always use vmcb01.<br /> <br /> As a result, if VMSAVE/VMLOAD is executed by an L2 guest and is not<br /> intercepted by L1, KVM will mistakenly use vmcb02. Always use vmcb01<br /> instead of the current VMCB.