Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Hardware breakpoints in Cheat Engine can cause the target process to commit suicide and restart #27

Open
Yalneh opened this issue Jun 10, 2024 · 1 comment
Open

Hardware breakpoints in Cheat Engine can cause the target process to commit suicide and restart #27

Yalneh opened this issue Jun 10, 2024 · 1 comment

Comments

@Yalneh
Copy link

Yalneh commented Jun 10, 2024

Hardware breakpoints in Cheat Engine can cause the target process to commit suicide and restart. For example, set a hardware breakpoint in the USER32.TranslateMessage of the task manager can cause the task manager to commit suicide and restart.
@Yalneh
Copy link
Author

Yalneh commented Jun 10, 2024

It is speculated that the breakpoint setting of Cheat Engine used a hardware breakpoint. When the task manager executed USER32. TranslateMessage, a debug interrupt was triggered, causing it to fall into the vmexit_exception_handler function of the vmm host. This function injected an EXCEPTION_VECTOR_SINGLE-STEP interrupt into the guest, but it caused KeGetCurrentThread() ->PreviousMode==KernelMode, which should have been the user mode.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Yalneh