GPU VulnDB

Database/Kernel, userspace & hypervisor

Azure Kubernetes Service kernel-mshv: improper privilege management allows local privilege escalation

CVSS 7.8CVE-2026-122986Kernel, userspace & hypervisorcurated

Impact

A local user with low privileges on an affected AKS node can raise their privileges. Microsoft rates the impact high for confidentiality, integrity and availability. The affected package is kernel-mshv, the Azure Linux kernel that runs on Microsoft Hypervisor, which AKS uses for hypervisor-isolated (pod sandboxing) node pools. If the escalation crosses that isolation boundary, a workload placed there to contain an untrusted tenant could get the access it was meant to be denied. The record does not say which component is at fault or whether the escalation stays inside the guest or reaches the host.

Who can reach it

Local, authenticated: a low-privilege user or workload on an AKS node running the affected kernel-mshv build. No user interaction is needed.

What to do

Take the AKS node image or kernel-mshv update that the Microsoft advisory names. The record gives no fixed version. Kernel updates on AKS usually ship through a node image upgrade, which cordons, drains and reimages each node, so plan capacity for GPU node pools where pods are slow to reschedule.

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.