Repository navigation
instrumentation.c: Use-after-Py_DECREF comparison in call_one_instrument #151524
Description
Bug report
Bug description:
Summary
At line 992-993, Py_DECREF(res) then res compared to &_PyInstrumentation_DISABLE. Using a potentially-freed pointer in comparison is UB per C standard.
This is a sub-issue of #146102 with gist details
CPython versions tested on:
CPython main branch
Operating systems tested on:
No response
Linked PRs
- gh-151524: Avoid using instrumentation callback result after Py_DECREF #151525
- [3.14] gh-151524: Make it clearer that
_PyInstrumentation_DISABLEis immortal in the code (GH-151525) #155349 - [3.15] gh-151524: Make it clearer that
_PyInstrumentation_DISABLEis immortal in the code (GH-151525) #155350 - [3.13] gh-151524: Make it clearer that
_PyInstrumentation_DISABLEis immortal in the code (GH-151525) #155351
Activity
pythongh-151524: Avoid using instrumentation callback result after Py…
gh-151524: Make it clearer that `_PyInstrumentation_DISABLE` is immor…
[3.13] gh-151524: Make it clearer that `_PyInstrumentation_DISABLE` i…
[3.14] gh-151524: Make it clearer that `_PyInstrumentation_DISABLE` i…
[3.15] gh-151524: Make it clearer that `_PyInstrumentation_DISABLE` i…
pythongh-151524: Make it clearer that `_PyInstrumentation_DISABLE` is…