MDEV-35516 sp_lex_keeper use after free - #5527
Open
grooverdan wants to merge 1 commit into
Open
Conversation
MSAN reported that there is a use after destruction. This is obvious in ~sp_lex_instr where the explict destructor is called, followed by the implict call to an already freed memory. Change ~sp_lex_keeper() to a destroy() method freeing the contents of object. Make the destructor call destroy(). There is a flag set so no duplicate freeing occurs. With this in place, ~sp_lex_instr() can call destroy, and leave the implict cleanup of the object to the ~sp_lex_keeper destructor.
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.
MSAN reported that there is a use after destruction. This is obvious in ~sp_lex_instr where the explict destructor is called, followed by the implict call to an already freed memory.
Change ~sp_lex_keeper() to a destroy() method
freeing the contents of object. Make the destructor call destroy(). There is a flag set so no duplicate freeing occurs.
With this in place, ~sp_lex_instr() can call destroy, and leave the implict cleanup of the object to the ~sp_lex_keeper destructor.