CVE-2026-64105

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-19. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 12, 2026

Advisory Details (4)

Auto-updated Aug 12, 2026
No patch confirmed yet.
generic

KVM: arm64: vgic: Free private_irqs when init fails after allocation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f19c354dbd457759dfcf1195ab4bdba2bb568323
generic

KVM: arm64: vgic: Free private_irqs when init fails after allocation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e690caa54a6139d98495ac69626807623520babd
generic

KVM: arm64: vgic: Free private_irqs when init fails after allocation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7023900b4988fb6f4a59d304d878003ff562e98d
generic

KVM: arm64: vgic: Free private_irqs when init fails after allocation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/173fb86e5519dbe7aabed1f5fa7456152a4a2e38

Vendor Advisories for CVE-2026-64105(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1

All Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 21× in last 7d / 81× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 111 total refreshes for this CVE.

  1. 2026-08-30 02:46 UTCEG score recompute
  2. 2026-08-30 02:46 UTCVendor advisory
  3. 2026-08-30 02:46 UTCGHSA enrichment
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-28 21:42 UTCEPSS rescore
  6. 2026-08-28 02:54 UTCEG score recompute
  7. 2026-08-28 02:54 UTCVendor advisory
  8. 2026-08-28 02:54 UTCGHSA enrichment
  9. 2026-08-27 02:25 UTCEG score recompute
  10. 2026-08-27 02:25 UTCVendor advisory
  11. 2026-08-27 02:25 UTCGHSA enrichment
  12. 2026-08-26 14:46 UTCEPSS rescore
  13. 2026-08-26 01:57 UTCEG score recompute
  14. 2026-08-26 01:57 UTCVendor advisory
  15. 2026-08-26 01:57 UTCGHSA enrichment
  16. 2026-08-25 13:49 UTCEPSS rescore
  17. 2026-08-25 01:29 UTCEG score recompute
  18. 2026-08-25 01:29 UTCVendor advisory
  19. 2026-08-25 01:29 UTCGHSA enrichment
  20. 2026-08-24 01:01 UTCVendor advisory
  21. 2026-08-24 01:01 UTCGHSA enrichment
  22. 2026-08-23 00:25 UTCEG score recompute
  23. 2026-08-23 00:25 UTCGHSA enrichment
  24. 2026-08-23 00:19 UTCEPSS rescore
  25. 2026-08-21 23:55 UTCEG score recompute
Show 75 more
  1. 2026-08-21 23:55 UTCVendor advisory
  2. 2026-08-21 23:55 UTCGHSA enrichment
  3. 2026-08-21 23:49 UTCEPSS rescore
  4. 2026-08-20 23:26 UTCVendor advisory
  5. 2026-08-20 23:26 UTCGHSA enrichment
  6. 2026-08-19 22:58 UTCEG score recompute
  7. 2026-08-19 22:58 UTCVendor advisory
  8. 2026-08-19 22:58 UTCGHSA enrichment
  9. 2026-08-19 17:04 UTCEPSS rescore
  10. 2026-08-18 21:49 UTCEG score recompute
  11. 2026-08-18 21:49 UTCVendor advisory
  12. 2026-08-18 21:49 UTCGHSA enrichment
  13. 2026-08-18 13:48 UTCEPSS rescore
  14. 2026-08-17 21:07 UTCEG score recompute
  15. 2026-08-17 21:07 UTCVendor advisory
  16. 2026-08-17 21:07 UTCGHSA enrichment
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-16 18:21 UTCEG score recompute
  19. 2026-08-16 18:21 UTCVendor advisory
  20. 2026-08-16 18:21 UTCGHSA enrichment
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-15 17:53 UTCEG score recompute
  23. 2026-08-15 17:53 UTCVendor advisory
  24. 2026-08-15 17:53 UTCGHSA enrichment
  25. 2026-08-15 01:30 UTCEPSS rescore
  26. 2026-08-14 17:24 UTCEG score recompute
  27. 2026-08-14 17:24 UTCVendor advisory
  28. 2026-08-14 17:24 UTCGHSA enrichment
  29. 2026-08-13 22:00 UTCEPSS rescore
  30. 2026-08-13 16:48 UTCEG score recompute
  31. 2026-08-13 16:48 UTCVendor advisory
  32. 2026-08-13 16:48 UTCGHSA enrichment
  33. 2026-08-12 15:51 UTCEG score recompute 5.50
  34. 2026-08-12 15:51 UTCVendor advisory
  35. 2026-08-12 15:51 UTCGHSA enrichment
  36. 2026-08-12 15:51 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  37. 2026-08-12 14:42 UTCVendor advisory
  38. 2026-08-12 14:42 UTCGHSA enrichment
  39. 2026-08-12 13:51 UTCEPSS rescore
  40. 2026-08-11 00:00 UTCEPSS rescore
  41. 2026-08-09 13:47 UTCEPSS rescore
  42. 2026-08-09 08:53 UTCVendor advisory
  43. 2026-08-09 08:53 UTCGHSA enrichment
  44. 2026-08-08 16:37 UTCEPSS rescore
  45. 2026-08-06 13:47 UTCEPSS rescore
  46. 2026-08-06 03:04 UTCVendor advisory
  47. 2026-08-06 03:04 UTCGHSA enrichment
  48. 2026-08-05 19:17 UTCEPSS rescore
  49. 2026-08-05 19:17 UTCEPSS rescore
  50. 2026-08-04 15:10 UTCEPSS rescore
  51. 2026-08-04 10:39 UTCEPSS rescore
  52. 2026-08-03 10:36 UTCEPSS rescore
  53. 2026-08-02 21:15 UTCVendor advisory
  54. 2026-08-02 21:15 UTCGHSA enrichment
  55. 2026-08-02 02:27 UTCEPSS rescore
  56. 2026-08-01 04:16 UTCEPSS rescore
  57. 2026-07-30 16:28 UTCEPSS rescore
  58. 2026-07-30 15:26 UTCEG score recompute
  59. 2026-07-30 15:26 UTCGHSA enrichment
  60. 2026-07-30 01:30 UTCEPSS rescore
  61. 2026-07-30 01:30 UTCEPSS rescore
  62. 2026-07-29 16:42 UTCGHSA enrichment
  63. 2026-07-28 15:37 UTCEPSS rescore
  64. 2026-07-27 14:14 UTCEPSS rescore
  65. 2026-07-26 14:54 UTCEPSS rescore
  66. 2026-07-26 14:54 UTCEPSS rescore
  67. 2026-07-26 10:53 UTCEG score recompute
  68. 2026-07-26 10:53 UTCVendor advisory
  69. 2026-07-26 10:53 UTCGHSA enrichment
  70. 2026-07-25 14:18 UTCEPSS rescore
  71. 2026-07-25 14:18 UTCEPSS rescore
  72. 2026-07-24 14:18 UTCEPSS rescore
  73. 2026-07-24 14:18 UTCEPSS rescore
  74. 2026-07-23 14:18 UTCEPSS rescore
  75. 2026-07-23 14:18 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-64105?
CVE-2026-64105 is a medium vulnerability published on July 19, 2026. 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 kvmvgicvcpu_destroy() call to the kvmsharehyp()…
When was CVE-2026-64105 disclosed?
CVE-2026-64105 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64105 actively exploited?
CVE-2026-64105 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.8% of all scored CVEs.
What is the CVSS score of CVE-2026-64105?
CVE-2026-64105 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64105?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64105, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64105

Explore →

Is Your Infrastructure Affected by CVE-2026-64105?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.