CVE-2026-46317

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-09. the CNA's CVSS baseline 8.8; sources differ by 0.0.

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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

KVM: arm64: Reassign nested_mmus array behind mmu_lock

kvm->arch.nested_mmus[] is walked under kvm->mmu_lock, including from the MMU notifier path (kvm_unmap_gfn_range() -> kvm_nested_s2_unmap()), which can run at any time. kvm_vcpu_init_nested() reallocates the array and frees the old buffer while holding only kvm->arch.config_lock, so such a walker can reference the freed array.

Allocate the new array outside of mmu_lock, as the allocation can sleep. Under the lock, copy the existing entries, fix up the back pointers and reassign the array. Free the old buffer after dropping the lock, as kvfree() can sleep as well.

CVSS v3
8.8
EG Score
8.8(high)
EPSS
3.0%
KEV
Not listed

Published

June 9, 2026

Last Modified

June 14, 2026

Advisory Details (3)

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

KVM: arm64: Reassign nested_mmus array behind mmu_lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/918450ad6010df6ecd2efde12a1409e011da22d6
generic

KVM: arm64: Reassign nested_mmus array behind mmu_lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/70543358fa08e0f7cebc3447c3b70fe97ad7aaa8
generic

KVM: arm64: Reassign nested_mmus array behind mmu_lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4424dbcb06d68e34e51c019a5781a7dc00731971

Vendor Advisories for CVE-2026-46317(1)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-46317?
CVE-2026-46317 is a high vulnerability published on June 9, 2026. In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Reassign nestedmmus array behind mmulock kvm->arch.nestedmmus[] is walked under kvm->mmulock, including from the MMU notifier path (kvmunmapgfnrange() -> kvmnesteds2unmap()), which can run at any time.…
When was CVE-2026-46317 disclosed?
CVE-2026-46317 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on June 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46317 actively exploited?
CVE-2026-46317 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46317?
CVE-2026-46317 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-46317?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46317, 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-46317

Explore →

Is Your Infrastructure Affected by CVE-2026-46317?

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