Ticket #19169 (new defect)

Opened 4 months ago

Last modified 5 weeks ago

CVE-2019-11135 causes Win10 Guests with Q2'19 Intel CPUs to get stuck with "IEM: wrmsr(0x122,0x0`00000003) -> #GP(0)"

Reported by: socratis Owned by:
Component: other Version: VirtualBox 6.0.8
Keywords: wrmsr 0x122, CVE-2019-11135, IA32_TSX_CTRL Cc:
Guest type: Windows Host type: Windows


When applying the  CVE-2019-11135 microcode update via Microsoft's  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:

This affects all VirtualBox > 6.0.8, hence the 6.0.10 version assigned.

Related discussion in the forums:

Change History

comment:1 Changed 4 months ago by socratis

  • Version changed from VirtualBox 6.0.10 to VirtualBox 6.0.8

Actually it's VirtualBox>6.0.6, not >6.0.8. Sorry about that.

"Version" corrected.

comment:2 Changed 4 months ago by MGA

You can add this cpu to the list : Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz

comment:3 Changed 3 months ago by nukeme1

you can add Intel® Core™ i7-9700 CPU @ 3.00GHz forums:

comment:4 Changed 8 weeks ago by jodhiroj

You can add Intel Core i5-8365U @ 1.60GHZ

comment:5 Changed 7 weeks ago by ramshankar

This looks like Windows 10 is writing to IA32_TSX_CTRL without properly verifying if the MSR is available.

Please provide feedback if the following test build works:

Windows host:

Note: Test builds won't work with UEFI secure boot enabled on your system. See for details.

Linux (64-bit) host:

Links expire automatically in ~14 days.

Last edited 7 weeks ago by ramshankar (previous) (diff)

comment:6 follow-up: ↓ 8 Changed 7 weeks ago by klaus

The fix is also in 6.1.4. Silently, because no one confirmed whether it really does what it should.

comment:7 Changed 7 weeks ago by sgadsby

Yes appears to be working for me in 6.1.4. I have successfully installed latest Windows Update and shutdown/start a couple of times.

C:\Program Files\Oracle\VirtualBox>VBoxManage.exe showvminfo "W10.C" |find "CPUProfile"
CPUProfile:                  host

I have not tested 6.0.17.

comment:8 in reply to: ↑ 6 Changed 5 weeks ago by jbnixdorf

Replying to klaus:

The fix is also in 6.1.4. Silently, because no one confirmed whether it really does what it should.

I answered in the forum that 6.0.17 is not working for me, none of my VMs are starting any more:

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use