That implies that GetCursorPos should not be used by Large Address Aware applications.
GetCursorInfo seems to work fine, so consider using it instead.
To reproduce the problem:
On Vista x64:
Set the following registry value to 0x100000:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management\AllocationPreference
and reboot
Enable the Large Address Aware (LAA) flag for the application, e.g. editbin /LARGEADDRESSAWARE test.exe
Run the application
GetCursorPos will fail but GetCursorInfo seems to work fine.