[issue36149] use of uninitialised memory in cPickle.

Change by Thomas Wouters : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue36149] use of uninitialised memory in cPickle.

Thomas Wouters added the comment: New changeset d9bf7f4198871132714cfe7d702baaa02206e9f1 by T. Wouters in branch '2.7': [2.7] bpo-36149 Fix potential use of uninitialized memory in cPickle (#12105) https://github.com/python/cpython/commit/d9bf7f4198871132714cfe7d702baaa02206e9f1 --

[issue36149] use of uninitialised memory in cPickle.

Change by Thomas Wouters : -- keywords: +patch pull_requests: +12112 stage: -> patch review ___ Python tracker ___ ___

[issue36149] use of uninitialised memory in cPickle.

New submission from Thomas Wouters : There is a bug in cPickle that makes it use uninitialised memory when reading a truncated pickle from a file (an actual C FILE*, not just any file-like object). Using MemorySanitizer: % ./python Python 2.7.15 (default, redacted, redacted)