gh-88116: Avoid undefined behavior when decoding varints in code objects #94375
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.
It seems like we'll fail to correctly decode a varint between INT_MAX
and UINT_MAX or if a signed varint is > INT_MAX / 2 or < INT_MIN / 2 as
this is written today. In fact, it might left shift a 1 into the sign
bit, which would be UB.
Indeed, this test program shows the issue:
As this prints -2.