CVE-2022-49559: KVM: x86: Drop WARNs that assert a triple fault never "escapes" from L2

Published Feb 26, 2025
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

KVM: x86: Drop WARNs that assert a triple fault never "escapes" from L2

Remove WARNs that sanity check that KVM never lets a triple fault for L2 escape and incorrectly end up in L1. In normal operation, the sanity check is perfectly valid, but it incorrectly assumes that it's impossible for userspace to induce KVMREQTRIPLEFAULT without bouncing through KVMRUN (which guarantees kvmchecknestedstate() will see and handle the triple fault).

The WARN can currently be triggered if userspace injects a machine check while L2 is active and CR4.MCE=0. And a future fix to allow save/restore of KVMREQTRIPLEFAULT, e.g. so that a synthesized triple fault isn't lost on migration, will make it trivially easy for userspace to trigger the WARN.

Clearing KVMREQTRIPLEFAULT when forcibly leaving guest mode is tempting, but wrong, especially if/when the request is saved/restored, e.g. if userspace restores events (including a triple fault) and then restores nested state (which may forcibly leave guest mode). Ignoring the fact that KVM doesn't currently provide the necessary APIs, it's userspace's responsibility to manage pending events during save/restore.

------------[ cut here ]------------ WARNING: CPU: 7 PID: 1399 at arch/x86/kvm/vmx/nested.c:4522 nestedvmxvmexit+0x7fe/0xd90 [kvmintel] Modules linked in: kvmintel kvm irqbypass CPU: 7 PID: 1399 Comm: statetest Not tainted 5.17.0-rc3+ #808 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 RIP: 0010:nestedvmxvmexit+0x7fe/0xd90 [kvmintel] Call Trace: <TASK> vmxleavenested+0x30/0x40 [kvmintel] vmxsetnestedstate+0xca/0x3e0 [kvmintel] kvmarchvcpuioctl+0xf49/0x13e0 [kvm] kvmvcpuioctl+0x4b9/0x660 [kvm] x64sysioctl+0x83/0xb0 dosyscall64+0x3b/0xc0 entrySYSCALL64afterhwframe+0x44/0xae </TASK> ---[ end trace 0000000000000000 ]---

Affected Software

8 affected componentsFixes available
Linux Kernel
Linux Linux kernel>=5.13<5.15.45
Linux Linux kernel>=5.16<5.17.13
Linux Linux kernel>=5.18<5.18.2
debian/linux<5.18.2-1
5.18.2-1
debian/linux<5.18.2-1
5.18.2-1
debian/linux<5.18.2-1
5.18.2-1
debian/linux
6.1.176-16.1.192-26.12.107-16.12.117-17.3.4-17.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.18.2-1
  2. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.192-2Fixed in 6.12.107-1Fixed in 6.12.117-1Fixed in 7.3.4-1Fixed in 7.3.5-1
  3. Operational

    Manage pending events, including triple faults, during save/restore of KVM state.

Event History

Feb 26, 2025
CVE Published
via MITRE·02:14 AM
Data Sourced
via MITRE·02:14 AM
Description
Data Sourced
via Red Hat·03:23 AM
DescriptionSeverityAffected Software
Data Sourced
via NVD·07:01 AM
RemedyDescriptionSeverityAffected Software
Data Sourced
via OSV·07:01 AM
DescriptionAffected Software

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203