Skip to content

Possible NULL pointer dereference in _PyThread_CurrentFrames #96582

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
kumaraditya303 opened this issue Sep 5, 2022 · 0 comments
Closed

Possible NULL pointer dereference in _PyThread_CurrentFrames #96582

kumaraditya303 opened this issue Sep 5, 2022 · 0 comments
Assignees
@kumaraditya303
Labels
3.11 only security fixes 3.12 only security fixes interpreter-core (Objects, Python, Grammar, and Parser dirs) type-bug An unexpected behavior, bug, or error type-crash A hard crash of the interpreter, possibly with a core dump

Comments

@kumaraditya303
Copy link
Contributor

_PyThread_CurrentFrames does not properly handles malloc failure in _PyFrame_GetFrameObject as it is lazily allocated when requested.
@kumaraditya303 kumaraditya303 added type-bug An unexpected behavior, bug, or error interpreter-core (Objects, Python, Grammar, and Parser dirs) 3.11 only security fixes type-crash A hard crash of the interpreter, possibly with a core dump 3.12 only security fixes labels Sep 5, 2022
@kumaraditya303 kumaraditya303 self-assigned this Sep 5, 2022
This was referenced Sep 5, 2022
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kumaraditya303 kumaraditya303

Labels
3.11 only security fixes 3.12 only security fixes interpreter-core (Objects, Python, Grammar, and Parser dirs) type-bug An unexpected behavior, bug, or error type-crash A hard crash of the interpreter, possibly with a core dump
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kumaraditya303