public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wangxuszcn at foxmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug malloc/25947] New: memory leak in muntrace
Date: Fri, 08 May 2020 03:55:09 +0000	[thread overview]
Message-ID: <bug-25947-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=25947

            Bug ID: 25947
           Summary: memory leak in muntrace
           Product: glibc
           Version: 2.3.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: malloc
          Assignee: unassigned at sourceware dot org
          Reporter: wangxuszcn at foxmail dot com
  Target Milestone: ---

Since glibc 2.32, stream buffer used by mallstream in mtrace() function, should
be freed in muntrace(), or 512 byte will leaked every call of mtrace().


Patches can be like this:
diff --git a/malloc/mtrace.c b/malloc/mtrace.c
index 7e7719d..b3bc5b0 100644
--- a/malloc/mtrace.c
+++ b/malloc/mtrace.c
@@ -365,4 +365,5 @@ muntrace (void)

   fprintf (f, "= End\n");
   fclose (f);
+  free (malloc_trace_buffer);
 }

Will any one request a CVE for this issue?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2020-05-08  3:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-08  3:55 wangxuszcn at foxmail dot com [this message]
2020-05-08  9:03 ` [Bug malloc/25947] " fw at deneb dot enyo.de
2020-05-08  9:50 ` wangxuszcn at foxmail dot com
2020-05-08 10:07 ` fw at deneb dot enyo.de
2021-08-12  1:14 ` siddhesh at sourceware dot org

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=bug-25947-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).