Fix null pointer dereference in ks_option for EVM backend#603
Open
SAY-5 wants to merge 1 commit into
Open
Conversation
Signed-off-by: Sai Asish Y <say.apm35@gmail.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
ks_option()dereferencesks->MAIunconditionally at the top of the function before checking the architecture. For LLVM-based backendsMAIis initialized duringks_open(), but the EVM backend returns early without setting it up, soks->MAIstaysNULL. As a result, callingks_option(ks, KS_OPT_SYNTAX, value)on an EVM engine crashes with a SIGSEGV before any option validation runs.This guards the
setRadix(16)call with aNULLcheck onks->MAI. TheKS_OPT_SYNTAXcase already rejects non-x86 architectures withKS_ERR_OPT_INVALID, so with the guard in place EVM now returns that error instead of dereferencing a null pointer. x86 behavior is unchanged sinceMAIis always set for that path.Fixes #602.