AZL-70468

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

KVM: x86/mmu: Treat NX as a valid SPTE bit for NPT

Treat the NX bit as valid when using NPT, as KVM will set the NX bit when the NX huge page mitigation is enabled (mindblowing) and trigger the WARN that fires on reserved SPTE bits being set.

KVM has required NX support for SVM since commit b26a71a1a5b9 ("KVM: SVM: Refuse to load kvm_amd if NX support is not available") for exactly this reason, but apparently it never occurred to anyone to actually test NPT with the mitigation enabled.

------------[ cut here ]------------ spte = 0x800000018a600ee7, level = 2, rsvd bits = 0x800f0000001fe000 WARNING: CPU: 152 PID: 15966 at arch/x86/kvm/mmu/spte.c:215 makespte+0x327/0x340 [kvm] Hardware name: Google, Inc. ArcadiaIT80/ArcadiaIT80, BIOS 10.48.0 01/27/2022 RIP: 0010:makespte+0x327/0x340 [kvm] Call Trace: <TASK> tdpmmumaphandletargetlevel+0xc3/0x230 [kvm] kvmtdpmmumap+0x343/0x3b0 [kvm] directpagefault+0x1ae/0x2a0 [kvm] kvmtdppagefault+0x7d/0x90 [kvm] kvmmmupagefault+0xfb/0x2e0 [kvm] npfinterception+0x55/0x90 [kvmamd] svminvokeexithandler+0x31/0xf0 [kvmamd] svmhandleexit+0xf6/0x1d0 [kvmamd] vcpuenterguest+0xb6d/0xee0 [kvm] ? kvmpmutriggerevent+0x6d/0x230 [kvm] vcpurun+0x65/0x2c0 [kvm] kvmarchvcpuioctlrun+0x355/0x610 [kvm] kvmvcpu_ioctl+0x551/0x610 [kvm] __sesysioctl+0x77/0xc0 __x64sysioctl+0x1d/0x20 dosyscall64+0x44/0xa0 entrySYSCALL64afterhwframe+0x46/0xb0 </TASK> ---[ end trace 0000000000000000 ]---