qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: QEMU Developers <qemu-devel@nongnu.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Brijesh Singh <brijesh.singh@amd.com>
Subject: Re: [PATCH] target/i386: Fix memory leak in sev_read_file_base64()
Date: Mon, 13 Sep 2021 13:33:35 +0100	[thread overview]
Message-ID: <CAFEAcA_p-AXGbP9UWwGVX5gKQv2jL8Fkt8M-Vr65MX-eHRnKjw@mail.gmail.com> (raw)
In-Reply-To: <20210820165650.2839-1-peter.maydell@linaro.org>

Ping?

thanks
-- PMM

On Fri, 20 Aug 2021 at 17:56, Peter Maydell <peter.maydell@linaro.org> wrote:
>
> In sev_read_file_base64() we call g_file_get_contents(), which
> allocates memory for the file contents.  We then base64-decode the
> contents (which allocates another buffer for the decoded data), but
> forgot to free the memory for the original file data.
>
> Use g_autofree to ensure that the file data is freed.
>
> Fixes: Coverity CID 1459997
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> Tested with 'make/make check' only...
>
>  target/i386/sev.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/target/i386/sev.c b/target/i386/sev.c
> index 83df8c09f6a..1e7833da1ab 100644
> --- a/target/i386/sev.c
> +++ b/target/i386/sev.c
> @@ -565,7 +565,7 @@ static int
>  sev_read_file_base64(const char *filename, guchar **data, gsize *len)
>  {
>      gsize sz;
> -    gchar *base64;
> +    g_autofree gchar *base64 = NULL;
>      GError *error = NULL;
>
>      if (!g_file_get_contents(filename, &base64, &sz, &error)) {
> --
> 2.20.1
>


      parent reply	other threads:[~2021-09-13 12:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-20 16:56 [PATCH] target/i386: Fix memory leak in sev_read_file_base64() Peter Maydell
2021-08-20 17:05 ` Philippe Mathieu-Daudé
2021-09-20 12:56   ` Paolo Bonzini
2021-09-13 12:33 ` Peter Maydell [this message]

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=CAFEAcA_p-AXGbP9UWwGVX5gKQv2jL8Fkt8M-Vr65MX-eHRnKjw@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=brijesh.singh@amd.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).