Host crash via uncleared KVM SRR1 value
Published Oct 28, 2021 · Updated Aug 4, 2024
Denial of service in Linux kernel powerpc KVM before 5.14.15 allows guest OS users to crash a Power8 host through crafted guest activity. idle_kvm_start_guest() fails to clear the saved SRR1 wakeup value after entering a guest, causing power7_offline() to interpret stale state as a host wakeup action. Only Power8 systems using Linux as the KVM hypervisor are exposed; PowerVM systems are unaffected, and successful triggering crashes the host.
Summary
What happened
Denial of service in Linux kernel powerpc KVM before 5.14.15 allows guest OS users to crash a Power8 host through crafted guest activity. idle_kvm_start_guest() fails to clear the saved SRR1 wakeup value after entering a guest, causing power7_offline() to interpret stale state as a host wakeup action. Only Power8 systems using Linux as the KVM hypervisor are exposed; PowerVM systems are unaffected, and successful triggering crashes the host.
The record
- CVE
- CVE-2021-43056
- Published
- Oct 28, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 28, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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