Host crash via unflushed SEV guest memory
Published Aug 26, 2022 · Updated Aug 2, 2024
Improper cache coherency handling in Linux kernel KVM before 5.18-rc4 allows local users to crash the host via an AMD SEV guest. When SEV guest memory is reclaimed or removed from KVM memory slots, the kernel fails to flush CPU caches across the noncoherent VM boundary, permitting silent data corruption. Exploitation requires low-privileged host access, KVM, and an AMD processor with SEV support; the bounded consequence is a host-kernel crash.
Summary
What happened
Improper cache coherency handling in Linux kernel KVM before 5.18-rc4 allows local users to crash the host via an AMD SEV guest. When SEV guest memory is reclaimed or removed from KVM memory slots, the kernel fails to flush CPU caches across the noncoherent VM boundary, permitting silent data corruption. Exploitation requires low-privileged host access, KVM, and an AMD processor with SEV support; the bounded consequence is a host-kernel crash.
The record
- CVE
- CVE-2022-0171
- Published
- Aug 26, 2022
- Updated
- Aug 2, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-459, CWE-212, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 26, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record 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=Fixed in kernel 5.18-rc4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Weakness, pattern, technique
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