← CVE Intelligence

CVE-2026-43133

KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation PUBLISHED

Description (CNA)

In the Linux kernel, the following vulnerability has been resolved: KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation Commit cc3ed80ae69f ("KVM: nSVM: always use vmcb01 to for vmsave/vmload of guest state") 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. 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.

Affected (CNA)

Vendor / productVersions
Linux / Linuxaffected cc3ed80ae69f454c3d904af9f65394a540099723 before 10063e1251c1485034a018236080792ad083dcc5; affected cc3ed80ae69f454c3d904af9f65394a540099723 before c3b7015000988ba35ecd5648f4b2283960f00543; affected cc3ed80ae69f454c3d904af9f65394a540099723 before 3880e331b0b31d0d5d3702b124f6c93539cd478a; affected cc3ed80ae69f454c3d904af9f65394a540099723 before fce2fd4a2ca05670a91015aacccf96a1c26268fd; affected cc3ed80ae69f454c3d904af9f65394a540099723 before d464cf1ed900d47c85393d40b00017b6adfc2e6c; affected cc3ed80ae69f454c3d904af9f65394a540099723 before 0004ecb798b30e90d7ebfe74efae2d9423315a64; affected cc3ed80ae69f454c3d904af9f65394a540099723 before 127ccae2c185f62e6ecb4bf24f9cb307e9b9c619
Linux / Linuxaffected 5.13; unaffected 0 before 5.13; unaffected 5.15.202 through 5.15.*; unaffected 6.1.165 through 6.1.*; unaffected 6.6.128 through 6.6.*; unaffected 6.12.75 through 6.12.*; unaffected 6.18.16 through 6.18.*; unaffected 6.19.6 through 6.19.*; unaffected 7.0 through *

CWE

No CWE identifiers supplied.

References

ADP enrichment

redhat-SADP

A flaw was found in the Linux kernel's Kernel-based Virtual Machine (KVM) nSVM module. When a nested virtual machine (L2 guest) executes VMSAVE/VMLOAD instructions, and these are not intercepted by the first-level hypervisor (L1), KVM incorrectly uses `vmcb02` instead of `vmcb01` for managing guest state. This incorrect Virtual Machine Control Block (VMCB) handling could lead to unexpected behavior or state corruption within the virtualized environment.

CISA-ADP

No English description supplied.

No references supplied.