Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix invalid access of NewRecoveryChallenge when memory allocation fails #168

Merged
merged 2 commits into from
Dec 6, 2023
Merged

Fix invalid access of NewRecoveryChallenge when memory allocation fails #168

merged 2 commits into from
Dec 6, 2023

Conversation

Nishanth1311
Copy link
Contributor

Description

If memory allocation for the NewChallenge variable should not be used. It will result in Invalid access at the following line.
NewChallenge->SerialNumber = 0;

With this change if memory allocation for the NewChallenge variable fails, EFI_OUT_OF_RESOURCES is returned

  • Impacts functionality? No
  • Impacts security? No
  • Breaking change? No
  • Includes tests? No
  • Includes documentation? No

How This Was Tested

Build passes with this change

Integration Instructions

N/A

@github-actions github-actions bot added the impact:non-functional Does not have a functional impact label Dec 6, 2023
@makubacki makubacki added the type:bug Something isn't working label Dec 6, 2023
@makubacki makubacki merged commit 8978086 into microsoft:main Dec 6, 2023
14 checks passed
ProjectMuBot referenced this pull request in microsoft/mu_tiano_platforms Dec 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impact:non-functional Does not have a functional impact type:bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants