From: Felix Willgerodt <felix.willgerodt@intel.com>
To: binutils@sourceware.org
Cc: Felix Willgerodt <felix.willgerodt@intel.com>
Subject: [PATCH 1/1] libctf: Fix double free in ctf_link_add_cu_mapping.
Date: Wed, 7 Dec 2022 15:11:37 +0100 [thread overview]
Message-ID: <20221207141137.1527113-1-felix.willgerodt@intel.com> (raw)
This fixes a potential double free which can occur if we jump to
oom_noerrno after the first free.
I am not very familiar with libctf, so any comments are welcome.
I am wondering if the right solution wouldn't be to free both t and f before
the "return 0". But I didn't fully understand the code and saw that other
users of ctf_dynhash_insert() also don't free the key manually.
libctf/ChangeLog:
* ctf-link.c (ctf_link_add_cu_mapping): Adjust freeing logic.
---
libctf/ctf-link.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/libctf/ctf-link.c b/libctf/ctf-link.c
index 702f2b4d5fe..e59e415eb41 100644
--- a/libctf/ctf-link.c
+++ b/libctf/ctf-link.c
@@ -430,8 +430,6 @@ ctf_link_add_cu_mapping (ctf_dict_t *fp, const char *from, const char *to)
goto oom_noerrno;
}
}
- else
- free (t);
if (ctf_dynhash_insert (one_out, f, NULL) < 0)
{
--
2.34.3
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next reply other threads:[~2022-12-07 14:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 14:11 Felix Willgerodt [this message]
2022-12-08 1:22 ` Alan Modra
2022-12-08 7:47 ` Willgerodt, Felix
2022-12-15 15:26 ` Nick Alcock
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=20221207141137.1527113-1-felix.willgerodt@intel.com \
--to=felix.willgerodt@intel.com \
--cc=binutils@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).