CVE-2026-46317

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM 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 — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

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(medium)
EG Risk
44(Track)
EG Risk 44/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
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

June 9, 2026

Last Modified

August 5, 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.

Patch Availability(15)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-09-14ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.17.0-1018.20~24.04.1) @ noble2026-09-14ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-09-14ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-09-14ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1030.30) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-14ubuntu
ubuntulinux-tools-azure-fde-6.17 (6.17.0-1018.18~24.04.1) @ noble2026-09-14ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-14ubuntu
ubuntulinux-tools-oracle-64k-6.17 (6.17.0-1019.19~24.04.3+1) @ noble2026-09-14ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-09-14ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-14ubuntu
ubuntulinux-tools-nvidia-hwe-24.04 (6.17.0-1031.31) @ noble2026-09-14ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-14ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-09-14ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1021.21~24.04.1) @ noble2026-09-14ubuntu

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.100-1 ... 7.2~rc7-1~exp1 (174 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (141 versions)7.0.12-1—

All Vendor Advisories

(15)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

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

Related CVEs(same vendor)

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 August 5, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 97.4% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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.

Start Free Scan →Browse All CVEs