Add simple, new auto-vex reachability: Emit OpenVEX vulnerable_code_not_in_execute_path statements when affected functions aren't imported by the release binary#55
Merged
Conversation
…ot_in_execute_path statements when affected functions aren't imported by the release binary Signed-off-by: Erick Bourgeois <erick@jeb.ca>
ebourgeois
force-pushed
the
phase-3-auto-vex-reachability
branch
from
8485ae5 to
b6a9a5e
Compare
prabhjotbawa
approved these changes
May 2, 2026
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
2 participants
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.
Add simple, new auto-vex reachability: Emit OpenVEX vulnerable_code_not_in_execute_path statements when affected functions aren't imported by the release binary