Set d_call to null to prevent potential use after free #739
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.
plugman_audio_callback in p25_recorder_decode is sometimes call when d_call is an invalid pointer. This seems to be some form of race condition where d_call has been freed immediately before the audio callback is called, causing a segmentation fault in the simplestream plugin on line 63 (
call->get_system()
). By setting d_call to null whenp25_recorder_decode::stop()
is called, we can check for it being invalid before a plugin ever sees it, preventing a use-after-free segmentation fault.