Description
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.
Product status
cc3ed80ae69f454c3d904af9f65394a540099723 (git) before 10063e1251c1485034a018236080792ad083dcc5
cc3ed80ae69f454c3d904af9f65394a540099723 (git) before c3b7015000988ba35ecd5648f4b2283960f00543
cc3ed80ae69f454c3d904af9f65394a540099723 (git) before 3880e331b0b31d0d5d3702b124f6c93539cd478a
cc3ed80ae69f454c3d904af9f65394a540099723 (git) before fce2fd4a2ca05670a91015aacccf96a1c26268fd
cc3ed80ae69f454c3d904af9f65394a540099723 (git) before d464cf1ed900d47c85393d40b00017b6adfc2e6c
cc3ed80ae69f454c3d904af9f65394a540099723 (git) before 0004ecb798b30e90d7ebfe74efae2d9423315a64
cc3ed80ae69f454c3d904af9f65394a540099723 (git) before 127ccae2c185f62e6ecb4bf24f9cb307e9b9c619
5.13
Any version before 5.13
5.15.202 (semver)
6.1.165 (semver)
6.6.128 (semver)
6.12.75 (semver)
6.18.16 (semver)
6.19.6 (semver)
7.0 (original_commit_for_fix)
References
git.kernel.org/...c/10063e1251c1485034a018236080792ad083dcc5
git.kernel.org/...c/c3b7015000988ba35ecd5648f4b2283960f00543
git.kernel.org/...c/3880e331b0b31d0d5d3702b124f6c93539cd478a
git.kernel.org/...c/fce2fd4a2ca05670a91015aacccf96a1c26268fd
git.kernel.org/...c/d464cf1ed900d47c85393d40b00017b6adfc2e6c
git.kernel.org/...c/0004ecb798b30e90d7ebfe74efae2d9423315a64
git.kernel.org/...c/127ccae2c185f62e6ecb4bf24f9cb307e9b9c619