In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: vgic: Free private_irqs when init fails after allocation Companion… (CVE-2026-64105)
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: vgic: Free private_irqs when init fails after allocation Companion to commit 250f25367b58 ("KVM: arm64: Tear down vGIC on failed vCPU creation"), which added the missing kvm_vgic_vcpu_destroy() call to the kvm_share_hyp() failure path in kvm_arch_vcpu_create(). The kvm_vgic_vcpu_init() failure path immediately above it has the same shape and still needs the same cleanup. Call kvm_vgic_vcpu_destroy() when kvm_vgic_vcpu_init() fails so private IRQs allocated before a redistributor iodev registration failure are released before the failed vCPU is freed.
AI Analysis
Technical Summary
The vulnerability (CVE-2026-64105) in the Linux kernel's KVM arm64 vGIC component relates to improper cleanup of private IRQs when kvm_vgic_vcpu_init() fails during virtual CPU creation. Previously, the failure path lacked a call to kvm_vgic_vcpu_destroy(), leading to resource leaks. This issue is a companion to a prior fix that added this cleanup call in a similar failure path. The resolution involves invoking kvm_vgic_vcpu_destroy() upon initialization failure to release allocated private IRQs before freeing the failed vCPU.
Potential Impact
The vulnerability could lead to resource leaks in the kernel when virtual CPUs fail to initialize properly, potentially affecting system stability or resource availability. There is no indication of direct security compromise or exploitation in the wild.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this issue by ensuring proper cleanup on initialization failure. Users should update to the kernel version containing this fix once available. Patch status is not explicitly confirmed in the provided data; check the official Linux kernel advisories for the exact fixed versions and apply updates accordingly.
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: vgic: Free private_irqs when init fails after allocation Companion… (CVE-2026-64105)
Description
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: vgic: Free private_irqs when init fails after allocation Companion to commit 250f25367b58 ("KVM: arm64: Tear down vGIC on failed vCPU creation"), which added the missing kvm_vgic_vcpu_destroy() call to the kvm_share_hyp() failure path in kvm_arch_vcpu_create(). The kvm_vgic_vcpu_init() failure path immediately above it has the same shape and still needs the same cleanup. Call kvm_vgic_vcpu_destroy() when kvm_vgic_vcpu_init() fails so private IRQs allocated before a redistributor iodev registration failure are released before the failed vCPU is freed.
CVSS v3.1
Score 5.5medium
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability (CVE-2026-64105) in the Linux kernel's KVM arm64 vGIC component relates to improper cleanup of private IRQs when kvm_vgic_vcpu_init() fails during virtual CPU creation. Previously, the failure path lacked a call to kvm_vgic_vcpu_destroy(), leading to resource leaks. This issue is a companion to a prior fix that added this cleanup call in a similar failure path. The resolution involves invoking kvm_vgic_vcpu_destroy() upon initialization failure to release allocated private IRQs before freeing the failed vCPU.
Potential Impact
The vulnerability could lead to resource leaks in the kernel when virtual CPUs fail to initialize properly, potentially affecting system stability or resource availability. There is no indication of direct security compromise or exploitation in the wild.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this issue by ensuring proper cleanup on initialization failure. Users should update to the kernel version containing this fix once available. Patch status is not explicitly confirmed in the provided data; check the official Linux kernel advisories for the exact fixed versions and apply updates accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-525g-3r8r-9mf7
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64105"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27a92a4a8d598912bbc9
Added to database: 07/19/2026, 19:38:17 UTC
Last enriched: 07/19/2026, 19:49:52 UTC
Last updated: 09/03/2026, 22:52:13 UTC
Views: 67
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.