Skip to main content
← All vulnerabilities
CVE-2026-43133

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

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 5.15.202, 6.1.165, 6.6.128, 6.12.75, 6.18.16, and 1 more
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

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.

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  3. Record last updated

Affected versions

  • Linux Linux

    From cc3ed80ae69f454c3d904af9f65394a540099723 · fixed in 10063e1251c1485034a018236080792ad083dcc5; From cc3ed80ae69f454c3d904af9f65394a540099723 · fixed in c3b7015000988ba35ecd5648f4b2283960f00543; From cc3ed80ae69f454c3d904af9f65394a540099723 · fixed in 3880e331b0b31d0d5d3702b124f6c93539cd478a; From cc3ed80ae69f454c3d904af9f65394a540099723 · fixed in fce2fd4a2ca05670a91015aacccf96a1c26268fd; From cc3ed80ae69f454c3d904af9f65394a540099723 · fixed in d464cf1ed900d47c85393d40b00017b6adfc2e6c; From cc3ed80ae69f454c3d904af9f65394a540099723 · fixed in 0004ecb798b30e90d7ebfe74efae2d9423315a64; From cc3ed80ae69f454c3d904af9f65394a540099723 · fixed in 127ccae2c185f62e6ecb4bf24f9cb307e9b9c619

  • Linux Linux

    5.13

  • KernelLinux

    From 5.13.0 · fixed in 5.15.202; From 5.16.0 · fixed in 6.1.165; From 6.2.0 · fixed in 6.6.128; From 6.7.0 · fixed in 6.12.75; From 6.13.0 · fixed in 6.18.16; From 6.19.0 · fixed in 6.19.6

References 7

git.kernel.org