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

core: fix potential double free in ta_open() #1970

Merged
merged 1 commit into from
Nov 23, 2017

Conversation

jenswi-linaro
Copy link
Contributor

ta_open() relies on the local variable shdr to be NULL unless it's a valid
pointer. alloc_and_copy_shdr() can in one code path update shdr and then
free it before returning.

The fix is in alloc_and_copy_shdr() to only set the returned shdr once
the pointer is to be returned.

Fixes: #1968
Signed-off-by: Jens Wiklander [email protected]

@jforissier
Copy link
Contributor

Reviewed-by: Jerome Forissier <[email protected]>

ta_open() relies on the local variable shdr to be NULL unless it's a valid
pointer. alloc_and_copy_shdr() can in one code path update shdr and then
free it before returning.

The fix is in alloc_and_copy_shdr() to only set the returned shdr once
the pointer is to be returned.

Reviewed-by: Jerome Forissier <[email protected]>
Fixes: OP-TEE#1968
Signed-off-by: Jens Wiklander <[email protected]>
@jenswi-linaro
Copy link
Contributor Author

Tag applied

@jforissier jforissier merged commit 2f47d83 into OP-TEE:master Nov 23, 2017
@jenswi-linaro jenswi-linaro deleted the fix_ta_open branch November 23, 2017 09:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Suspicious potential double free in ta_open() of ree_fs_ta.c
2 participants