KVM: nVMX: Hide shadow VMCS right after VMCLEAR
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 355f4fb1405ec29d0fac49b4d41fcd78cbd455d5 · < 8001d2ce9d9bd09118ce523aef595aa094573ae3| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
KVM: nVMX: Hide shadow VMCS right after VMCLEAR
free_nested() frees the shadow VMCS while vmcs01 still points to it. But because it is asynchronous with respect to loaded_vmcs_clear(), the vCPU might migrate before the pointer is cleared and __loaded_vmcs_clear() may then execute VMCLEAR.
The VMCS needs to stay attached until its explicit VMCLEAR completes, but then it can be hidden and the page safely freed.
From the CVE record · Linux
The Linux kernel's KVM nVMX code can free a shadow VMCS while another VMCS still points to it, creating a use-after-free risk during VMCLEAR. The input does not specify what an attacker could achieve or whether exploitation requires network access, authentication, or user interaction.
Engineers running Linux kernels with KVM nVMX should check their versions; affected versions are not specified.