From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] tools/proftool: fix use-after-free
Date: Wed, 7 Oct 2015 11:42:31 -0400 [thread overview]
Message-ID: <20151007154231.GP3829@bill-the-cat> (raw)
In-Reply-To: <56152DC9.3060009@freescale.com>
On Wed, Oct 07, 2015 at 04:35:53PM +0200, Vincent Stehl? wrote:
> On 10/07/2015 04:19 PM, Tom Rini wrote:
> ..
> > Were you in the Coverity talk too? :)
>
> Hi Tom,
>
> No, I was not following that talk, sorry.
Ah, coincidence then.
> ..
> > free(line);
> > - return regex_report_error(&line->regex, err, "compile",
> > + err = regex_report_error(&line->regex, err, "compile",
> > tok);
> > + return err;
>
> I am not sure you solve the problem this way. Indeed the structure
> pointed to by the line pointer will still have been freed before use
> even this way. Who knows what the memory contains when regerror() will
> access &line->regex, which is contained into the freed structure?
Er, bah. That's what I get for writing something in the middle of
listening to a talk too. I meant to also move the free() to after the
regex_report_error call and just avoid adding another variable.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20151007/b1004c0c/attachment.sig>
next prev parent reply other threads:[~2015-10-07 15:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 13:48 [U-Boot] [PATCH] tools/proftool: fix use-after-free Vincent Stehlé
2015-10-07 14:19 ` Tom Rini
2015-10-07 14:35 ` Vincent Stehlé
2015-10-07 15:42 ` Tom Rini [this message]
2015-11-17 1:40 ` [U-Boot] " Tom Rini
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=20151007154231.GP3829@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.