Host kernel crash via stale nested guest state
Published Oct 24, 2022 · Updated May 7, 2025
Use-after-free in KVM AMD nested virtualization in Linux Kernel 6.0.3 and earlier allows guest OS users to crash the host kernel. During kvm_vcpu_reset(), KVM clears guest-mode flags without leaving nested mode, frees vmcb02 with the nested state, and then continues using it. Exploitation requires control of an L1 guest on an AMD host with nested virtualization enabled and an L2 guest whose shutdown or reset is not intercepted; the bounded consequence is an L0 kernel panic.
Summary
What happened
Use-after-free in KVM AMD nested virtualization in Linux Kernel 6.0.3 and earlier allows guest OS users to crash the host kernel. During kvm_vcpu_reset(), KVM clears guest-mode flags without leaving nested mode, frees vmcb02 with the nested state, and then continues using it. Exploitation requires control of an L1 guest on an AMD host with nested virtualization enabled and an L2 guest whose shutdown or reset is not intercepted; the bounded consequence is an L0 kernel panic.
The record
- CVE
- CVE-2022-3344
- Published
- Oct 24, 2022
- Updated
- May 7, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-440, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 24, 2022CVE publishedPublication date reported by the CVE source.
- May 7, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Affected versions <= 6.0.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo