gh-154781: Zero the in_wstr() buffer in curses - #154782
Merged
serhiy-storchaka merged 3 commits intoJul 29, 2026
Merged
Conversation
winnwstr() only writes the terminating null when it stored at least one character, so with n of 0 the result was read from uninitialized memory. Use PyMem_Calloc, like in_wchstr() already does.
Member
There was a problem hiding this comment.
Should not this be enough?
Suggested change
| PyObject *res = PyUnicode_FromWideChar(buf, rtn); |
Contributor
Author
There was a problem hiding this comment.
Nice call! Changed it.
mbeijen
pushed a commit
to mbeijen/cpython
that referenced
this pull request
Aug 14, 2026
…54782) in_wstr() searched the result for a terminating null, but winnwstr() writes one only if it stored at least one character. Use the number of characters it returns as the length.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
winnwstr()only writes the terminating null when it stored at least one character, soin_wstr(y, x, 0)read the result from uninitialized memory and usually raisedValueError: character U+xxxxxxxx is not in range. UsePyMem_Calloc, likein_wchstr()already does since gh-152503.
in_wstr()is new in 3.16, so there is no NEWS entry.