Repository navigation
gh-158063: Fix out-of-bounds read when comparing decimal signal dicts - #158069
Open
lazerg wants to merge 1 commit into
Open
lazerg wants to merge 1 commit into
lazerg wants to merge 1 commit into
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
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.
signaldict_richcompare() checked SdFlagAddr(w) before it knew w was a signal dict, so comparing flags or traps with anything else (e.g. None) read the flags pointer from past the end of that object. The NULL check on w now only runs when w is a signal dict. Other objects fall through to the existing dict/NotImplemented handling.