Bug 2467065 (CVE-2026-43133) - CVE-2026-43133 kernel: KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation
Summary: CVE-2026-43133 kernel: KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation
Keywords:
Status: NEW
Alias: CVE-2026-43133
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-05-06 13:02 UTC by OSIDB Bzimport
Modified: 2026-09-15 09:19 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:65334 0 None None None 2026-09-08 11:35:05 UTC
Red Hat Product Errata RHSA-2026:66180 0 None None None 2026-09-09 22:05:05 UTC
Red Hat Product Errata RHSA-2026:66357 0 None None None 2026-09-15 09:19:14 UTC
Red Hat Product Errata RHSA-2026:67468 0 None None None 2026-09-15 00:47:03 UTC
Red Hat Product Errata RHSA-2026:67469 0 None None None 2026-09-15 00:24:50 UTC

Description OSIDB Bzimport 2026-05-06 13:02:22 UTC 
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.
Comment 1 Keith Grant 2026-05-06 18:05:23 UTC 
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026050622-CVE-2026-43133-ffea@gregkh/T
Comment 7 errata-xmlrpc 2026-09-08 11:35:04 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:65334 https://access.redhat.com/errata/RHSA-2026:65334
Comment 8 errata-xmlrpc 2026-09-09 22:05:03 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:66180 https://access.redhat.com/errata/RHSA-2026:66180
Comment 9 Jon Orris 2026-09-15 00:24:47 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:67469 https://access.redhat.com/errata/RHSA-2026:67469
Comment 10 Jon Orris 2026-09-15 00:47:00 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:67468 https://access.redhat.com/errata/RHSA-2026:67468
Comment 11 Jon Orris 2026-09-15 09:19:12 UTC 
This issue has been addressed in the following products:

  Red Hat OpenShift Container Platform 4.22

Via RHSA-2026:66357 https://access.redhat.com/errata/RHSA-2026:66357
Note You need to log in before you can comment on or make changes to this bug.