Prevent BitChunks length overflow#9818
Merged
alamb merged 1 commit intoapache:mainfrom Apr 25, 2026
Merged
Conversation
Dandandan
approved these changes
Apr 25, 2026
19 tasks
Contributor
Author
|
Thank you @Dandandan |
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.
Which issue does this PR close?
Rationale for this change
BitChunks used unchecked usize arithmetic when validating bit offset plus length. In optimized builds, very large lengths could wrap this bounds check before constructing the iterator state.
What changes are included in this PR?
This adds checked arithmetic for BitChunks bounds validation
Are these changes tested?
Yes. This adds regression coverage for overflowing bit offset plus length validation.
Are there any user-facing changes?
Invalid BitChunks inputs whose offset and length cannot be represented without overflow now panic consistently. There are no API changes.