-
-
Notifications
You must be signed in to change notification settings - Fork 34.3k
gh-92888: Fix memoryview bad __index__ use after free
#92946
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
Merged
Fidget-Spinner
merged 12 commits into
python:main
from
Fidget-Spinner:fix_memoryview_auf
Jun 17, 2022
Merged
Changes from 1 commit
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
73ffb29
Fix memoryview bad `__index__` use after free
Fidget-Spinner 3581de7
📜🤖 Added by blurb_it.
blurb-it[bot] 43c66d6
stylistic nits
Fidget-Spinner 18b921f
Merge branch 'fix_memoryview_auf' of https://github.com/Fidget-Spinne…
Fidget-Spinner 2f3c04f
Fix whitespace
Fidget-Spinner a250b02
Use more comprehensive tests by Serhiy
Fidget-Spinner c818990
Add more tests by Serhiy
Fidget-Spinner 42a706c
Fix newline
Fidget-Spinner b650764
Fix for tuple index
Fidget-Spinner 47bd91f
Address review
Fidget-Spinner 6890713
Address Victor's review
Fidget-Spinner d3edf74
re-add ba=None
Fidget-Spinner File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Fix newline
- Loading branch information
commit 42a706c9597a7e7b06cc4380fef5a742053e083f
There are no files selected for viewing
3 changes: 2 additions & 1 deletion
3
Misc/NEWS.d/next/Security/2022-05-19-08-53-07.gh-issue-92888.TLtR9W.rst
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1 +1,2 @@ | ||
| Fix ``memoryview`` use after free when accessing the backing buffer in certain cases. | ||
| Fix ``memoryview`` use after free when accessing the backing buffer in certain cases. | ||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I propose to mention more explicitly that the protection is about released views:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not always an exception is raised.
The bug was in reading or wring the freed memory. Now it is prevented -- you either get an exception or free the memory after reading. @Fidget-Spinner's description is more correct.
I am going to address such inconsistency in a separate issue.