RFR: 8330611: AES-CTR vector intrinsic may read out of bounds (x86_64, AVX-512)

[Sandhya Viswanathan]

On Fri, 19 Apr 2024 00:04:41 GMT, Martin Balao <mbalao at openjdk.org> wrote:

> We would like to propose a fix for 8330611.
> 
> To avoid an out of bounds memory read when the input's size is not multiple of the block size, we read the plaintext/ciphertext tail in 8, 4, 2 and 1 byte batches depending on what it is guaranteed to be available by 'len_reg'. This behavior replaces the read of 16 bytes of input upfront and later discard of spurious data.
> 
> While we add 3 extra instructions + 3 extra memory reads in the worst case —to the same cache line probably—, the performance impact of this fix should be low because it only occurs at the end of the input and when its length is not multiple of the block size.
> 
> A reliable test case for this bug is hard to develop because we would need accurate heap allocation. The fact that spuriously read data is silently discarded most of the time makes this bug harder to observe. No regressions have been observed in the compiler/codegen/aes jtreg category. Additionally, we verified the fix manually with the debugger.
> 
> This work is in collaboration with @franferrax .

src/hotspot/cpu/x86/stubGenerator_x86_64_aes.cpp line 2184:

> 2182:   const Register rounds = rax;
> 2183:   const Register pos = r12;
> 2184:   const Register tail = r13;

Better to use tail = r15 here. It looks to me that using tail as r13 will cause problems on Windows platform. used_addr is set as r13 in generate_counterMode_VectorAESCrypt() (line 398) for Windows platform and is needed at line 2655 so there is a conflict if we overwrite r13 as tail.

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/18849#discussion_r1577032982