[3.12] gh-148395: Fix a possible UAF in {LZMA,BZ2,_Zlib}Decompressor (GH-148396)#148503
[3.12] gh-148395: Fix a possible UAF in {LZMA,BZ2,_Zlib}Decompressor (GH-148396)#148503miss-islington wants to merge 3 commits into
{LZMA,BZ2,_Zlib}Decompressor (GH-148396)#148503Conversation
…pythonGH-148396) Fix dangling input pointer after `MemoryError` in _lzma/_bz2/_ZlibDecompressor.decompress (cherry picked from commit 8fc66ae) Co-authored-by: Stan Ulbrych <stan@python.org>
|
Damn, too many tabs and I edited the wrong backport :-/ |
This comment was marked as spam.
This comment was marked as spam.
|
@StanFromIreland is the review still ongoing, or is this PR stalled? |
|
This will be merged before the next release. |
|
It's interesting that from at least out of 5 different branches (3.10 to 3.14), all the PRs have been merged already but 3.12. At least that's what I got from #148395 If I may, do you know why? |
|
They have different release managers, and it's up to their discretion. |
Is there a date for this? I was under the impression that once the major version goes into security support, releases happen at the discretion of the manager. But here it looks like there is some timeline for the next release. BTW, I appreciate your prompt response |
|
There's no timeline. |
5 participants
Fix dangling input pointer after
MemoryErrorin _lzma/_bz2/_ZlibDecompressor.decompress(cherry picked from commit 8fc66ae)
Co-authored-by: Stan Ulbrych stan@python.org
{LZMA,BZ2,_Zlib}Decompressor#148395