Repository navigation
Conversation
Callback can free an object resulting in UAF if we have relied on the object for visiting the next item in the chain. Fix is to use `finalize_garbage` approach of walking the object gc generation list directly maintaing and moving it into a tempoary list before calling callback
Failure case is crashing the whole test suite, also may not be reliable
Contributor
|
@nascheme Could you please take a look? |
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
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.
Callback can free an object resulting in UAF if we have relied on the object for visiting the next item in the chain.
Fix is to use
finalize_garbageapproach of walking the object gc generation list directly maintaing and moving it into a tempoary list before calling callbackvisit_generation()#160663