Jun 17, 2022 · May 19, 2022 · May 19, 2022 · May 19, 2022 · May 20, 2022 · May 21, 2022
diff --git a/Misc/NEWS.d/next/Security/2022-05-19-08-53-07.gh-issue-92888.TLtR9W.rst b/Misc/NEWS.d/next/Security/2022-05-19-08-53-07.gh-issue-92888.TLtR9W.rst
 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.
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.
Copy link Member vstinnerMay 23, 2022 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: `If a memoryview is released while getting or setting an item, raise an exception.For example, converting an object to an index can execute arbitrary Pythoncode which can indirectly release the memoryview.` Copy link Member serhiy-storchakaMay 25, 2022 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.