Skip to content

Conversation

@shipilev
Copy link
Member

@shipilev shipilev commented Oct 23, 2025

See the bug for symptoms and discussion.

In short, in newly added intrinsic in JDK 24, there is a potential read out of Java heap if key array is at the edge of it, which will crash JVM. And that read is redundant for the code path in question, we only use it in the subsequent blocks that we never actually enter in the problematic case. So we never see any failures in testing: the only observable effect is SEGV on uncommitted heap access. It is somewhat similar to JDK-8330611 we have fixed in other place. But this one can be caught with the explicit range check in debug code.

I opted to keep this patch very simple, because I would backport it to 25u shortly after we integrate to mainline. It just moves the read down to the block where it is actually needed. Note that aes_192 and aes_256 labels are red herring in this code, they are unbound; you can even remove them without any bulid errors. The actual thing that drives path selection is NROUNDS -- that one is derived from the key array length -- and we are just doing the read too early.

Additional testing:

  • Linux x86_64 server fastdebug, com/sun/crypto/provider/Cipher compiler/codegen/aes (fails with range check only, passes with entire patch)
  • Linux x86_64 server fastdebug, all on AVX-512 machine

Progress

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

Issue

  • JDK-8370318: AES-GCM vector intrinsic may read out of bounds (x86_64, AVX-512) (Bug - P3)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 27951

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

Using diff file

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

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Oct 23, 2025

👋 Welcome back shade! 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
Copy link

openjdk bot commented Oct 23, 2025

@shipilev This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8370318: AES-GCM vector intrinsic may read out of bounds (x86_64, AVX-512)

Reviewed-by: kvn, roland

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 79 new commits pushed to the master branch:

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

@openjdk openjdk bot added the hotspot-compiler hotspot-compiler-dev@openjdk.org label Oct 23, 2025
@openjdk
Copy link

openjdk bot commented Oct 23, 2025

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

  • hotspot-compiler

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 added the rfr Pull request is ready for review label Oct 23, 2025
@mlbridge
Copy link

mlbridge bot commented Oct 23, 2025

Webrevs

Copy link
Contributor

@vnkozlov vnkozlov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Oct 23, 2025
@shipilev
Copy link
Member Author

Thanks! I think I need another Review before I can integrate.

@shipilev
Copy link
Member Author

Friendly reminder. Thanks!

Copy link
Contributor

@rwestrel rwestrel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

@shipilev
Copy link
Member Author

Thank you! Here goes.

/integrate

@openjdk
Copy link

openjdk bot commented Oct 27, 2025

Going to push as commit 7bb490c.
Since your change was applied there have been 81 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Oct 27, 2025
@openjdk openjdk bot closed this Oct 27, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Oct 27, 2025
@openjdk
Copy link

openjdk bot commented Oct 27, 2025

@shipilev Pushed as commit 7bb490c.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

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

Labels

hotspot-compiler hotspot-compiler-dev@openjdk.org integrated Pull request has been integrated

Development

Successfully merging this pull request may close these issues.

3 participants