Fix out-of-bound (OOB) input read in AES-XTS Decrypt in AVX-512 implementation #2227
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.
Issues:
Resolves #V1681992550
Description of changes:
Fix instruction that caused out-of-bound read in the input reading of the 16x loop (which processes a batch of 16 blocks of AES, 1 block = 16 bytes). This was triggered on lengths that are in the range [16k * (16 bytes), (16k +3)* (16 bytes)-1], k = 1, 2, ... The instruction was reading up to 3*16 bytes beyond the input length bound.
The fix was inspired by the 8x loop in
aws-lc/crypto/fipsmodule/aes/asm/aesni-xts-avx512.pl
Line 2544 in becf578
The existing unit tests cover those cases but there were no explicit memory protections and ASAN doesn't instrument assembly code to check for out-of-bound reads even when the contiguous memory is explicitly poisoned.
The OOB read existed only on the decrypt path which rereads the last block when looping over 16 blocks (and over 8 blocks, but the instruction in the 8x case linked above didn't over-read) .
Call-outs:
N/A
Testing:
On c6i, without the fix, the unit test segfaults
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and the ISC license.