Tracker / CVE-2026-43133
CVE-2026-43133
High 7.9
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 products and versions
| linux | linux_kernel · 5.13 → 5.15.202 |
|---|---|
| linux | linux_kernel · 5.16 → 6.1.165 |
| linux | linux_kernel · 6.13 → 6.18.16 |
| linux | linux_kernel · 6.19 → 6.19.6 |
| linux | linux_kernel · 6.2 → 6.6.128 |
| linux | linux_kernel · 6.7 → 6.12.75 |
Analysis
This page is not indexable yet.Until it carries original analysis — what it actually exposes, how to check in two minutes whether a system was touched, what to do if it was — the page stays noindex. The database decides that, not the template.