CVE-2026-43133

Last refreshed2026-10-17

Status: UPDATED | Advisory ID: CVE-2026-43133

Key Details

CVE	CVE-2026-43133
CVSS Score / Version	7.9 (High) / CVSS v3.1
Updated	2026-10-16
CVSS Vector	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:H`
CVSS Prose	attack vector is local; attack complexity is low; privileges required is low; user interaction is none; scope is changed; confidentiality impact is low; integrity impact is low; availability impact is high.
Affected products	Linux Kernel, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9, and Red Hat OpenShift Container Platform 4
Classified as	CWE-628 (Function Call with Incorrectly Specified Arguments)

Vendor	Product	Affected Versions	Patch Status
Linux	Linux Kernel
Red Hat	Red Hat Enterprise Linux 10
Red Hat	Red Hat Enterprise Linux 8
Red Hat	Red Hat Enterprise Linux 9
Red Hat	Red Hat OpenShift Container Platform 4

Vendor

Product

Affected Versions

Patch Status

Linux

Linux Kernel

Red Hat

Red Hat Enterprise Linux 10

Red Hat

Red Hat Enterprise Linux 8

Red Hat

Red Hat Enterprise Linux 9

Red Hat

Red Hat OpenShift Container Platform 4

Subsystems	OT Supporting Infrastructure
Sectors	All Sectors

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. (NVD)

Monitor Linux's and Red Hat's web pages for any future patch releases.

Source	Reference
NVD	https://nvd.nist.gov/vuln/detail/CVE-2026-43133
CVE	https://www.cve.org/CVERecord?id=CVE-2026-43133

Source

Reference

NVD

CVE