VirtualBox

Ticket #19169 (new defect)

Opened 20 months ago

Last modified 13 months 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

Description

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:  https://forums.virtualbox.org/viewtopic.php?f=2&t=95783

Change History

comment:1 Changed 20 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 20 months ago by MGA

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

comment:3 Changed 19 months ago by nukeme1

you can add Intel® Core™ i7-9700 CPU @ 3.00GHz forums:  https://forums.virtualbox.org/viewtopic.php?f=6&t=96457&p=467979

comment:4 Changed 18 months ago by jodhiroj

You can add Intel Core i5-8365U @ 1.60GHZ
 https://forums.virtualbox.org/viewtopic.php?f=6&t=96825

comment:5 Changed 18 months 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:
https://www.virtualbox.org/download/testcase/VirtualBox-6.0.17-136150-Win.exe

Note: Test builds won't work with UEFI secure boot enabled on your system. See https://www.virtualbox.org/wiki/Testbuilds#InstallingWindowstestbuilds for details.

Linux (64-bit) host:
https://www.virtualbox.org/download/testcase/VirtualBox-6.0.17-136150-Linux_amd64.run

Links expire automatically in ~14 days.

Last edited 18 months ago by ramshankar (previous) (diff)

comment:6 follow-up: ↓ 8 Changed 18 months 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 18 months 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 ; follow-up: ↓ 9 Changed 17 months 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:  https://forums.virtualbox.org/viewtopic.php?f=2&t=95783&start=45#p470440

comment:9 in reply to: ↑ 8 Changed 15 months ago by fth0

Replying to 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:  https://forums.virtualbox.org/viewtopic.php?f=2&t=95783&start=45#p470440

Your tests with test build 6.0.17 show a totally different error (vboxdrv being stuck, reported in the VBoxHardening.log).

Do you still have the problem indicated by the bug title ('wrmsr(0x122, ...', reported in VBox.log)?

Last edited 15 months ago by fth0 (previous) (diff)

comment:10 Changed 13 months ago by jbnixdorf

I now updated to the latest version 6.1.10 and for me the issue is fixed.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use