CVE-2026-46316

CRITICALPre-NVD 9.39.3
EchelonGraph scoreMEDIUM confidence

Score 9.3 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-09. a secondary CVSS source baseline 9.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.3
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.3Exploit: NoneExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

KVM: arm64: vgic-its: Drop the translation cache reference only for the erased entry

vgic_its_invalidate_cache() walks the per-ITS translation cache with xa_for_each() and drops the cache's reference on each entry with vgic_put_irq(). It puts the iterated pointer, though, rather than the value returned by xa_erase().

The function is called from contexts that do not exclude one another: the ITS command handlers hold its_lock, the GITS_CTLR write path holds cmd_lock, and the path that clears EnableLPIs in a redistributor's GICR_CTLR holds neither. Two or more of them can drain the same cache concurrently, and if each one observes the same entry, erases it and then puts it, the single reference the cache holds on that entry is dropped more than once. The entry can then be freed while an ITE still maps it.

xa_erase() is atomic and returns the previous entry, so put only the entry that this context actually removed. The cache reference is then dropped exactly once per entry even when the invalidations run concurrently, and the behavior is unchanged when only one context runs.

CVSS v3
9.3
EG Score
9.3(medium)
EG Risk
46(Track)
EG Risk 46/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
Severity93% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
10.4%
KEV
Not listed

Published

June 9, 2026

Last Modified

July 22, 2026

Advisory Details (4)

Auto-updated Jun 14, 2026
No patch confirmed yet.
generic

KVM: arm64: vgic-its: Drop the translation cache reference only for the erased entry - kernel/git/stable/linux.git - Linux kernel stable tree

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

KVM: arm64: vgic-its: Drop the translation cache reference only for the erased entry - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9121f4605ab94969f62d1b5714ca3c6c69bd202f
generic

KVM: arm64: vgic-its: Drop the translation cache reference only for the erased entry - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2bbc395e81bd29c543a0529a678327e932a7ec69
generic

KVM: arm64: vgic-its: Drop the translation cache reference only for the erased entry - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/13031fb6b8357fbbcded2a7f4cba73e4781ee594

Patch Availability(13)

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.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(10)

Data Freshness Timeline

(refreshed 10× in last 7d / 163× 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 224 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-46316?
CVE-2026-46316 is a critical vulnerability published on June 9, 2026. In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: vgic-its: Drop the translation cache reference only for the erased entry vgicitsinvalidate_cache() walks the per-ITS translation cache with xaforeach() and drops the cache's reference on each entry with vgicputirq(). It…
When was CVE-2026-46316 disclosed?
CVE-2026-46316 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46316 actively exploited?
CVE-2026-46316 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 10.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46316?
CVE-2026-46316 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2026-46316?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46316, 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

Explore the affected products and dependency analysis for CVE-2026-46316

Explore →

Is Your Infrastructure Affected by CVE-2026-46316?

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