[3.7] bpo-34408: Prevent a null pointer dereference and resource leakage in PyInterpreterState_New()
(GH-8767)
#13237
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.
A pointer in
PyInterpreterState_New()
could have beenNULL
when being dereferenced.Memory was leaked in
PyInterpreterState_New()
when taking some error-handling code path.(cherry picked from commit 95d630e)
Co-authored-by: Pablo Galindo [email protected]