KVM: x86: nSVM: fix potential NULL derefernce on nested migration
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
5.15.255.16.115.17In the Linux kernel, the following vulnerability has been resolved:
KVM: x86: nSVM: fix potential NULL derefernce on nested migration
Turns out that due to review feedback and/or rebases I accidentally moved the call to nested_svm_load_cr3 to be too early, before the NPT is enabled, which is very wrong to do.
KVM can't even access guest memory at that point as nested NPT is needed for that, and of course it won't initialize the walk_mmu, which is main issue the patch was addressing.
Fix this for real.
From the CVE record · Linux
A call to nested_svm_load_cr3 occurs before nested NPT is enabled during KVM nSVM nested migration. This can cause a NULL dereference; the input does not establish how an attacker could trigger it or what access or interaction would be required.
Engineers running the Linux kernel with KVM nSVM should check their versions; affected versions are not specified.