crypto: fix UB in computing max message size #21462
Closed
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.
Before this commit it computed
(1<<(8*(15-iv_len)))-1
foriv_len>=11
and that reduces to
(1<<32)-1
foriv_len==11
. Left-shifting pastthe sign bit and overflowing a signed integral type are both undefined
behaviors.
This commit switches to fixed values and restricts the
iv_len==11
case to
INT_MAX
, as was already the case for alliv_len<=10
.