Skip to main content
VulnerabilityPublished Updated

CVE-2026-64105: Linux kernel · KVM: arm64: vgic: Free private_irqs when init fails after allocation

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in f19c354dbd457759dfcf1195ab4bdba2bb568323 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:49 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in f19c354dbd457759dfcf1195ab4bdba2bb568323, e690caa54a6139d98495ac69626807623520babd, 7023900b4988fb6f4a59d304d878003ff562e98d +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade Linux kernel to f19c354dbd457759dfcf1195ab4bdba2bb568323, e690caa54a6139d98495ac69626807623520babd, 7023900b4988fb6f4a59d304d878003ff562e98d or 173fb86e5519dbe7aabed1f5fa7456152a4a2e38.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 03b3d00a70b55857439511c1b558ca00a99f4126, < f19c354dbd457759dfcf1195ab4bdba2bb568323
Fixed in
  • f19c354dbd457759dfcf1195ab4bdba2bb568323
LinuxLinuxAffected
  • ≥ 03b3d00a70b55857439511c1b558ca00a99f4126, < e690caa54a6139d98495ac69626807623520babd
Fixed in
  • e690caa54a6139d98495ac69626807623520babd
LinuxLinuxAffected
  • ≥ 03b3d00a70b55857439511c1b558ca00a99f4126, < 7023900b4988fb6f4a59d304d878003ff562e98d
Fixed in
  • 7023900b4988fb6f4a59d304d878003ff562e98d
LinuxLinuxAffected
  • ≥ 03b3d00a70b55857439511c1b558ca00a99f4126, < 173fb86e5519dbe7aabed1f5fa7456152a4a2e38
Fixed in
  • 173fb86e5519dbe7aabed1f5fa7456152a4a2e38
LinuxLinuxAffected
  • =6.10
Fixed in–

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.

References

Community reviews

Loading reviews…