Host-kernel crash via stale redistributor registration
Published Nov 5, 2024 · Updated Aug 5, 2026
Use-after-free in arm64 KVM in Linux 6.11 through 6.11.5 allows local users with /dev/kvm access to crash the host kernel. On failed vCPU creation, __kvm_vgic_vcpu_destroy() leaves the redistributor MMIO device registered, so teardown later dereferences freed vCPU memory. Access to /dev/kvm and an arm64 host with GICv3 are required; reusing a vCPU ID or exhausting file descriptors creates the failure path.
Summary
What happened
Use-after-free in arm64 KVM in Linux 6.11 through 6.11.5 allows local users with /dev/kvm access to crash the host kernel. On failed vCPU creation, __kvm_vgic_vcpu_destroy() leaves the redistributor MMIO device registered, so teardown later dereferences freed vCPU memory. Access to /dev/kvm and an arm64 host with GICv3 are required; reusing a vCPU ID or exhausting file descriptors creates the failure path.
The record
- CVE
- CVE-2024-50114
- Published
- Nov 5, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 5, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record 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=6.11
- Affected versionversion=f616506754d34bcfdbfbc7508b562e5c98461e9a <6bcc2890b883ba1d16b8942937750565f6e9db0d
- Affected versionversion=f616506754d34bcfdbfbc7508b562e5c98461e9a <ae8f8b37610269009326f4318df161206c59843e
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.
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