
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 could create system instability. Using a debugger to step into a syscall instruction might 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.
The following isses 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.0 only. For the related patch for ESX Server 3.0.1, refer to http://kb.vmware.com/kb/5095559.
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-7104553.tgz
The md5 checksum output should match the following:
81c4f33331a4cbc565c1d9a44b1ea4fc ESX-7104553.tgz
# tar -xvzf ESX-7104553.tgz
# cd ESX-7104553
| Note: All virtual machines on the host must be either shut down or migrated using VMotion before applying the patch. No reboot of the ESX Server host is required after applying this patch. |
# 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-7104553 update
For example, if the host is called depot:
# esxupdate –r file:///depot/var/updates/ESX-7104553 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-7104553 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.