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 10:19:29 -0400 [thread overview]
Message-ID: <20151007141929.GO3829@bill-the-cat> (raw)
In-Reply-To: <1444225728-23057-1-git-send-email-vincent.stehle@freescale.com>
On Wed, Oct 07, 2015 at 03:48:48PM +0200, Vincent Stehl? wrote:
> The read_trace_config() can dereference the line pointer after freeing
> it on its error path. Avoid that.
>
> This was found by Coverity Scan.
>
> Signed-off-by: Vincent Stehl? <vincent.stehle@freescale.com>
> Cc: Simon Glass <sjg@chromium.org>
Were you in the Coverity talk too? :) I saw this error as well today
now. I was actually thinking along the lines of:
diff --git a/tools/proftool.c b/tools/proftool.c
index 9ce7a77..b3d3057 100644
--- a/tools/proftool.c
+++ b/tools/proftool.c
@@ -433,8 +433,9 @@ static int read_trace_config(FILE *fin)
err = regcomp(&line->regex, tok, REG_NOSUB);
if (err) {
free(line);
- return regex_report_error(&line->regex, err, "compile",
+ err = regex_report_error(&line->regex, err, "compile",
tok);
+ return err;
}
/* link this new one to the end of the list */
--
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/38022432/attachment.sig>
next prev parent reply other threads:[~2015-10-07 14:19 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 [this message]
2015-10-07 14:35 ` Vincent Stehlé
2015-10-07 15:42 ` Tom Rini
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=20151007141929.GO3829@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox