Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Enabling Hypervisor-Specific Mitigations for Machine Check Error on Page Size Change (MCEPSC) Speculative-Execution vulnerability (CVE-2018-12207) (59139)

Last Updated: 2/28/2024Categories: SecurityTotal Views: 25937Language:
JapaneseEnglish

6 like this article

Subscribe to get an email
newsletter with new updates

6 people found this helpful Please provide article feedback:

Purpose

Speculative-Execution vulnerabilities have been disclosed which affect Intel processors. Hypervisor-Specific Mitigations for one of these vulnerabilities, identified by CVE-2018-12207, is not enabled by default. This article documents the instructions for enabling this mitigation on ESXi. For information on the security implication of CVE-2018-12207, see VMSA-2019-0020 .

Cause

This issue occurs due to the Machine Check Error on Page Size Change (MCEPSC) Speculative-Execution vulnerability identified by CVE-2018-12207.

Resolution

Important: Performance impact data found in KB76050 should be reviewed prior to enabling this mitigation.

Mitigations can be applied at either the host or guest level.

To enable Hypervisor-Specific Mitigations for CVE-2018-12207 at the host level perform the following steps:

Update the ESXi host with the patches detailed in section 3a of VMSA-2019-0020 .

Connect to the host with an SSH session.

Edit the /etc/vmware/config file.

Add this line:

monitor.if_pschange_mc_workaround = "TRUE"

Perform one of these options to apply the changes:

Power Off and then Power On the virtual machines (Restart is insufficient)

Suspend and resume the virtual machines

vMotion the VM to a different patched host

vMotion the VM to a different unpatched host and then back to a patched host

Verify that the vmware.log file shows that that disable_mmu_largepages has been applied. You will see an entry similar to:

YYYY-MM-DDTHH:MM:SS.349Z| vmx| I125: DICT monitor.if_pschange_mc_workaround = "TRUE"

Note: The change to /etc/vmware/config should normally persist across reboot. However, if you are using host profiles, you should recapture the host profile after editing /etc/vmware/config to ensure that the host profile does not remove it.

To enable Hypervisor-Specific Mitigations for CVE-2018-12207 at the guest level perform the following steps:

Update ESXi with the appropriate patches detailed in section 3a of VMSA-2019-0020 .

Navigate to where the VM is stored and edit the VM_name.vmx.

Add this line:

monitor.if_pschange_mc_workaround = "TRUE"

Perform one of these options to apply the changes

Power Off and then Power On the virtual machine (Restart is insufficient)

Suspend and resume the virtual machine

vMotion the VM to a different patched host

vMotion the VM to a different unpatched host and then back to a patched host

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
JapaneseEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware vSphere ESXi

VMware ESXi

Related Versions:

VMware vSphere ESXi 7.0.x

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

VMware vSphere ESXi 6.0

Take Our Survey

Support Assistant