Host service interruption via reentrant event deadlock
Published Mar 25, 2022 · Updated Aug 3, 2024
Improper locking in libvirt's libxl driver allows guest OS users to deadlock or crash the host's libvirtd daemon by rebooting. The event callback searches for and locks a virDomainObj while a shutdown thread already holds that object and calls into libxl, allowing a pending shutdown event to reenter the handler and wait on the same lock. Exploitation requires control of a guest on a Xen host using the libxl driver; repeated guest reboots can hang or crash libvirtd and interrupt host virtualization management.
Summary
What happened
Improper locking in libvirt's libxl driver allows guest OS users to deadlock or crash the host's libvirtd daemon by rebooting. The event callback searches for and locks a virDomainObj while a shutdown thread already holds that object and calls into libxl, allowing a pending shutdown event to reenter the handler and wait on the same lock. Exploitation requires control of a guest on a Xen host using the libxl driver; repeated guest reboots can hang or crash libvirtd and interrupt host virtualization management.
The record
- CVE
- CVE-2021-4147
- Published
- Mar 25, 2022
- Updated
- Aug 3, 2024
- Vendor
- libvirt
- Product
- libvirt
- Classifications
- CWE-667, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 25, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=libvirt 2.33.0
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