Fix potential memory leak in RSAPSS#1186
Merged
jasonkatonica merged 1 commit intoIBM:java11from Feb 13, 2026
Merged
Conversation
jasonkatonica
requested review from
JinhangZhang,
KostasTsiounis,
johnpeck-us-ibm and
taoliult
johnpeck-us-ibm
approved these changes
Feb 13, 2026
jasonkatonica
force-pushed
the
katonica/issue1138/rsapssmemleak-java11
branch
from
e1393b4 to
b6a43fd
Compare
taoliult
approved these changes
Feb 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
When creating a new context with ICC_EVP_MD_CTX_new potential failures can occur. In the case that this API fails we should release the entire ockDigest structure upon failure.
Fixes: #1138
Back-ported from: #1169
Signed-off-by: Jason Katonica katonica@us.ibm.com