
Search the Knowledge Base: |
Search the Knowledge Base: |
This patch fixes an issue where in a 64-bit Windows guest, on a 64-bit host, debugging local programs might create system instability. Using a debugger to step into a syscall instruction can corrupt the virtual machine's register context. This corruption produces unpredictable results including corrupted stack pointers, kernel bugchecks, or vmware-vmx process failures.
Thanks to Ken Johnson for identifying this issue.
The Common Vulnerabilities and Exposures project (cve.mitre.org) assigned the name CVE-2007-1876 to this issue.
This following issues are resolved in this patch:
This issue is fixed in ESX Server 3.0.2 and higher.
This patch is for ESX Server 3.0.1 only. For the related patch for ESX Server 3.0.0, refer to http://kb.vmware.com/kb/7104553.
Download and verify the patch bundle as follows:
# mkdir -p /var/updates
Note: VMware recommends that you use the updates directory.
# cd /var/updates
# md5sum ESX-5095559.tgz
The md5 checksum output should match the following:
bcded4127598c22d47f06ab03366d2f8 ESX-5095559.tgz
# tar -xvzf ESX-5095559.tgz
# cd ESX-5095559
After you have downloaded and extracted the archive, and if you are in the directory you created above, install the update using the following command:
# esxupdate update
If you want to run esxupdate from a different directory, you must specify the bundle path in the command:
# esxupdate -r file://<directory>/ESX-5095559 update
For example, if the host is called depot:
# esxupdate –r file:///depot/var/updates/ESX-5095559 update
During the update process, logs appear on the terminal. You can specify the verbosity of esxupdate logs by using the -v option as shown below:
# esxupdate -v 10 -r file://<directory>/ESX-5095559 update
For more information on using esxupdate, refer to the Patch Management for ESX Server 3 tech note at http://www.vmware.com/pdf/esx3_esxupdate.pdf.