CVE-2026-46076

HIGHPre-NVD 7.97.9—
EchelonGraph scoreMEDIUM confidence

Score 7.9 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. a secondary CVSS source baseline 7.9; sources differ by 0.0.

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

A fix is available — apply it.

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

KVM: nSVM: Raise #UD if unhandled VMMCALL isn't intercepted by L1

Explicitly synthesize a #UD for VMMCALL if L2 is active, L1 does NOT want to intercept VMMCALL, nested_svm_l2_tlb_flush_enabled() is true, and the hypercall is something other than one of the supported Hyper-V hypercalls. When all of the above conditions are met, KVM will intercept VMMCALL but never forward it to L1, i.e. will let L2 make hypercalls as if it were L1.

The TLFS says a whole lot of nothing about this scenario, so go with the architectural behavior, which says that VMMCALL #UDs if it's not intercepted.

Opportunistically do a 2-for-1 stub trade by stub-ifying the new API instead of the helpers it uses. The last remaining "single" stub will soon be dropped as well.

[sean: rewrite changelog and comment, tag for stable, remove defunct stubs]

CVSS v3
7.9
EG Score
7.9(medium)
EPSS
2.3%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 24, 2026

Advisory Details (4)

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

KVM: nSVM: Raise #UD if unhandled VMMCALL isn't intercepted by L1 - kernel/git/stable/linux.git - Linux kernel stable tree

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

KVM: nSVM: Raise #UD if unhandled VMMCALL isn't intercepted by L1 - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/924d721fae95687acedbaf624a094ed0e8b67104
generic

KVM: nSVM: Raise #UD if unhandled VMMCALL isn't intercepted by L1 - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5fb4a5f361565f5b629d8a8fe5288ce8463c5727
generic

KVM: nSVM: Raise #UD if unhandled VMMCALL isn't intercepted by L1 - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/009c0f726abeaa67aad1d96b883bdce01d405ce2

Vendor Advisories for CVE-2026-46076(2)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1013.13) @ resolute2026-07-11ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1014.14) @ resolute2026-07-11ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1008.8) @ resolute2026-07-11ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-27.27) @ resolute2026-07-11ubuntu

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.

All Vendor Advisories

(4)

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 / 67× 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 164 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-46076?
CVE-2026-46076 is a high vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: KVM: nSVM: Raise #UD if unhandled VMMCALL isn't intercepted by L1 Explicitly synthesize a #UD for VMMCALL if L2 is active, L1 does NOT want to intercept VMMCALL, nestedsvml2tlbflush_enabled() is true, and the hypercall is something…
When was CVE-2026-46076 disclosed?
CVE-2026-46076 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46076 actively exploited?
CVE-2026-46076 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46076?
CVE-2026-46076 has a CVSS v3 base score of 7.9 (NVD).
How do I remediate CVE-2026-46076?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46076, 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-46076

Explore →

Is Your Infrastructure Affected by CVE-2026-46076?

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

Start Free Scan →Browse All CVEs