You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Valgrind: Conditional jump or move depends on uninitialised value in ob_digit[0] of PyLongObject #119022
There are several cases, where ob_digit[0] of PyLongObject will not be initialized before evaluation.
I fixed that issue in Python 3.11.8 with this patch - it also concerns Python 3.11.9:
For example, one case is in longobject.c:922 in _PyLong_FromByteArray() if numsignificantbytes==0.
First, I fixed it locally in _PyLong_FromByteArray() but than I found similar cases in other functions.
Therefore, I decided to initialize ob_digit[0] right in _PyLong_New() in order to catch all situations.
Kind regards,
Ove
Activity
sweeneyde commentedon May 14, 2024
Just an initial comment: I'm assuming this was fixed in 3.12+ by #102509.
3.11 looks like it's only accepting security fixes now, but I'm not sure whether this qualifies or not.
sobolevn commentedon May 14, 2024
Yes, this was fixed in #102510
3.11 is security only, so it was not backported.
3.12+ are fixed.