Skip to content

8390765: [PPC64] AES Crypto intrinsics may access memory beyond the key array - #32465

Open
TheRealMDoerr wants to merge 1 commit into
openjdk:masterfrom
TheRealMDoerr:8390765_PPC64_AES
Open

8390765: [PPC64] AES Crypto intrinsics may access memory beyond the key array#32465
TheRealMDoerr wants to merge 1 commit into
openjdk:masterfrom
TheRealMDoerr:8390765_PPC64_AES

Conversation

@TheRealMDoerr

@TheRealMDoerr TheRealMDoerr commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

The old implementation of the AES stubs uses instruction sequences based on lvx and vperm instructions to handle unaligned accesses to the key array. Accesses beyond that array are possible (see JBS issue).

I've replaced the problematic sequences by instructions which can handle unaligned memory accesses. I'm using the better Power9 instructions if available and Power8 instructions else. (The AES intrinsics require Power8 as minimum.)

Note that Big Endian is much easier to handle because "lxvd2x, lxvw4x, lxvh8x, lxvb16x, and lxvx exhibit identical behavior in Big-Endian mode." (Power ISA).

No performance regression has been observed.
Also tested with -XX:+UnlockDiagnosticVMOptions -XX:PowerArchitecturePPC64=8



Progress

  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue
  • Change must be properly reviewed (2 reviews required, with at least 1 Reviewer, 1 Author)

Issue

  • JDK-8390765: [PPC64] AES Crypto intrinsics may access memory beyond the key array (Bug - P3)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/32465/head:pull/32465
$ git checkout pull/32465

Update a local copy of the PR:
$ git checkout pull/32465
$ git pull https://git.openjdk.org/jdk.git pull/32465/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 32465

View PR using the GUI difftool:
$ git pr show -t 32465

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/32465.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper

bridgekeeper Bot commented Aug 20, 2026

Copy link
Copy Markdown

👋 Welcome back mdoerr! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk

openjdk Bot commented Aug 20, 2026

Copy link
Copy Markdown

❗ This change is not yet ready to be integrated.
See the Progress checklist in the description for automated requirements.

@openjdk openjdk Bot added the hotspot hotspot-dev@openjdk.org label Aug 20, 2026
@openjdk

openjdk Bot commented Aug 20, 2026

Copy link
Copy Markdown

@TheRealMDoerr The following label will be automatically applied to this pull request:

  • hotspot

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

@openjdk

openjdk Bot commented Aug 20, 2026

Copy link
Copy Markdown

The total number of required reviews for this PR has been set to 2 based on the presence of this label: hotspot. This can be overridden with the /reviewers command.

@openjdk openjdk Bot added the rfr Pull request is ready for review label Aug 20, 2026
@mlbridge

mlbridge Bot commented Aug 20, 2026

Copy link
Copy Markdown

Webrevs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

hotspot hotspot-dev@openjdk.org rfr Pull request is ready for review

Development

Successfully merging this pull request may close these issues.

1 participant