[New-bugs-announce] [issue36459] A possible double PyMem_FREE() due to tokenizer.c's tok_nextc()
Zackery Spytz
report at bugs.python.org
Thu Mar 28 00:33:19 EDT 2019
New submission from Zackery Spytz <zspytz at gmail.com>:
Commit cb90c89de14aab636739b3e810cf949e47b54a0c added a PyMem_FREE(tok->buf) call in tok_nextc() if a PyMem_REALLOC() call fails. This will cause a double free when PyTokenizer_Free() is called on the tokenizer state.
----------
components: Interpreter Core
messages: 339013
nosy: ZackerySpytz
priority: normal
severity: normal
status: open
title: A possible double PyMem_FREE() due to tokenizer.c's tok_nextc()
type: crash
versions: Python 2.7, Python 3.7, Python 3.8
_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36459>
_______________________________________
More information about the New-bugs-announce
mailing list