From: Tom Rix <trix@redhat.com>
To: Ben Boeckel <me@benboeckel.net>
Cc: jejb@linux.ibm.com, jarkko@kernel.org, zohar@linux.ibm.com,
dhowells@redhat.com, jmorris@namei.org, serge@hallyn.com,
linux-integrity@vger.kernel.org, keyrings@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org,
Colin King <colin.king@canonical.com>
Subject: Re: [PATCH] KEYS: trusted: fix memory leak
Date: Fri, 30 Apr 2021 16:08:56 -0700 [thread overview]
Message-ID: <baecdb22-6433-7ad0-6c9e-75f4c5d1201d@redhat.com> (raw)
In-Reply-To: <YIxfehTLhWe58sNE@erythro>
On 4/30/21 12:50 PM, Ben Boeckel wrote:
> On Fri, Apr 30, 2021 at 11:58:10 -0700, trix@redhat.com wrote:
>> From: Tom Rix <trix@redhat.com>
>>
>> Static analysis reports this problem
>> trusted-keys/trusted_tpm1.c:496:10: warning: Potential memory leak
>> return ret;
>> ^~~
>>
>> In tpm_seal() some failure handling returns directly, without
>> freeing memory.
>>
>> Fixes: 5df16caada3f ("KEYS: trusted: Fix incorrect handling of tpm_get_random()")
>> Signed-off-by: Tom Rix <trix@redhat.com>
>> ---
>> security/keys/trusted-keys/trusted_tpm1.c | 8 +++++---
>> 1 file changed, 5 insertions(+), 3 deletions(-)
>>
>> diff --git a/security/keys/trusted-keys/trusted_tpm1.c b/security/keys/trusted-keys/trusted_tpm1.c
>> index 469394550801..aa108bea6739 100644
>> --- a/security/keys/trusted-keys/trusted_tpm1.c
>> +++ b/security/keys/trusted-keys/trusted_tpm1.c
>> @@ -493,10 +493,12 @@ static int tpm_seal(struct tpm_buf *tb, uint16_t keytype,
>>
>> ret = tpm_get_random(chip, td->nonceodd, TPM_NONCE_SIZE);
>> if (ret < 0)
>> - return ret;
>> + goto out;
>>
>> - if (ret != TPM_NONCE_SIZE)
>> - return -EIO;
>> + if (ret != TPM_NONCE_SIZE) {
>> + ret = -EIO;
>> + goto out;
>> + }
>>
>> ordinal = htonl(TPM_ORD_SEAL);
>> datsize = htonl(datalen);
> I see this patch also submitted by Colin (Cc'd) in Message-Id:
>
> <20210430113724.110746-1-colin.king@canonical.com>
Let's use Colin's.
Tom
>
> To my eyes, the commit message seems a bit better over there.
>
> --Ben
>
next prev parent reply other threads:[~2021-04-30 23:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 18:58 trix
2021-04-30 19:50 ` Ben Boeckel
2021-04-30 23:08 ` Tom Rix [this message]
2021-05-03 14:56 ` Jarkko Sakkinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=baecdb22-6433-7ad0-6c9e-75f4c5d1201d@redhat.com \
--to=trix@redhat.com \
--cc=colin.king@canonical.com \
--cc=dhowells@redhat.com \
--cc=jarkko@kernel.org \
--cc=jejb@linux.ibm.com \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=me@benboeckel.net \
--cc=serge@hallyn.com \
--cc=zohar@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®