﻿id	summary	reporter	owner	description	type	status	component	version	resolution	keywords	cc	guest	host
19169	"CVE-2019-11135 causes Win10 Guests with Q2'19 Intel CPUs to get stuck with ""IEM: wrmsr(0x122,0x0`00000003) -> #GP(0)"""	Socratis		"When applying the [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11135 CVE-2019-11135] microcode update via Microsoft's [https://support.microsoft.com/en-us/help/4524570/windows-10-update-kb4524570 2019-11 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4524570)], a Win10 (64-bit) guest will not boot completely, but will rather get stuck with:
{{{
00:00:07.800331 IEM: wrmsr(0x122,0x0`00000003) -> #GP(0)
}}}
Intel CPUs that have been affected so far are all Q2'19:
* [https://ark.intel.com/content/www/us/en/ark/products/193563/intel-core-i7-8665u-processor-8m-cache-up-to-4-80-ghz.html Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz]
* [https://ark.intel.com/content/www/us/en/ark/products/192987/intel-core-i9-9880h-processor-16m-cache-up-to-4-80-ghz.html Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz]
* [https://ark.intel.com/content/www/us/en/ark/products/192993/intel-xeon-e-2286m-processor-16m-cache-2-40-ghz.html Intel(R) Xeon(R) E-2286M  CPU @ 2.40GHz]

This affects all !VirtualBox > 6.0.8, hence the 6.0.10 version assigned.

Related discussion in the forums: https://forums.virtualbox.org/viewtopic.php?f=2&t=95783"	defect	new	other	VirtualBox 6.0.8		wrmsr 0x122, CVE-2019-11135, IA32_TSX_CTRL		Windows	Windows
