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.
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
bpo-45329: Fix freed memory access in pyexpat.c #28649
Conversation
|
LGTM, but please add a NEWS entry. https://blurb-it.herokuapp.com/ |
Misc/NEWS.d/next/Core and Builtins/2021-10-01-11-17-45.bpo-45329.vtqRvA.rst
Outdated
Show resolved
Hide resolved
|
I found that the segmentation fault occurs with expat So this patch might be useful on system which uses old expat... |
|
Thanks @y-tag for the PR, and @serhiy-storchaka for merging it |
(cherry picked from commit 0742abd) Co-authored-by: TAGAMI Yukihiro <tagami.yukihiro@gmail.com>
|
GH-28692 is a backport of this pull request to the 3.10 branch. |
(cherry picked from commit 0742abd) Co-authored-by: TAGAMI Yukihiro <tagami.yukihiro@gmail.com>
|
GH-28693 is a backport of this pull request to the 3.9 branch. |
|
Thank you for your contribution TAGAMI-san! |
|
Thank you too! |
https://bugs.python.org/issue45329
xmlparse_clear(self)callsclear_handlers(self, 0)clear_handlers(self, 0)accessesself->itselfxmlparse_clear(self)would be done beforeXML_ParserFree(self->itself)https://bugs.python.org/issue45329
The text was updated successfully, but these errors were encountered: