CVE-2026-43133

Medium

Elevated severity or exploit probability.

CVSS base

7.9 HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:H

EPSS — probability of exploitation (30 days)

0.1%

3.2th percentile

CISA KEV

Not listed

Weakness / dates

CWE-628

Published 2026-05-06 · modified 2026-09-15

CVSS breakdown

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:H

Attack Vector	L	Local
Attack Complexity	L	Low
Privileges Required	L	Low
User Interaction	N	None
Scope	C	Changed
Confidentiality	L	Low
Integrity	L	Low
Availability	H	High

Timeline

2026-05-06 — Published (NVD)
2026-09-15 — Last modified (NVD)

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.

Affected

linux

References

Official: NVD · CVE.org