Skip to content

bpo-43362: Fix bad free in py_sha3_new_impl function #24702

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

Closed
wants to merge 1 commit into from

Conversation

alexhenrie
Copy link
Contributor

@alexhenrie alexhenrie commented Mar 2, 2021

Initializing buf.obj to NULL earlier in the function prevents the possibility of PyBuffer_Release being called on an invalid object.

https://bugs.python.org/issue43362

Copy link

@auvipy auvipy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you check function declaration isn’t a prototype [-Wstrict-prototypes]? also doesn't this need some change in tests?

@github-actions
Copy link

github-actions bot commented Apr 3, 2021

This PR is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale Stale PR or inactive for long period of time. label Apr 3, 2021
@tiran tiran removed skip news stale Stale PR or inactive for long period of time. labels Apr 17, 2021
@tiran
Copy link
Member

tiran commented Apr 17, 2021

Please rebase the PR and provide a blurb (news entry).

Copy link
Member

@tiran tiran left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please rebase the PR and provide a blurb (news entry).

@bedevere-bot
Copy link

A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated.

Once you have made the requested changes, please leave a comment on this pull request containing the phrase I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request.

@tiran
Copy link
Member

tiran commented Apr 17, 2021

I have found another potential problem and opened #25463. You are mentioned as co-author. Thanks for your assistance!

@tiran tiran closed this Apr 17, 2021
@alexhenrie
Copy link
Contributor Author

@tiran Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants