Fix handling for "0x48 0xff 0x25" instruction in hook_create_stub function #91
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…stub function to resolve the bug where imported functions fail to correctly jump to the original execution flow after hooking on x86-64 samples under Windows 10/Windows 11.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue:
In x86-64 architecture, particularly under Windows 10 and Windows 11, imported functions fail to correctly jump to the original execution flow after hooking.
Changes:
Added handling for the "0x48 0xff 0x25" instruction in the
hook_create_stubfunction to resolve the issue. This change ensures correct redirection to the original execution path after hooking imported functions.Testing:
Thoroughly tested on Windows 10 and Windows 11 environments to validate the fix's effectiveness and stability.