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/25945] New: memory block return by tcache_get() may contain anather valid memory block pointer, leading to memory leak Date: Fri, 08 May 2020 03:35:18 +0000 [thread overview] Message-ID: <bug-25945-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=25945 Bug ID: 25945 Summary: memory block return by tcache_get() may contain anather valid memory block pointer, leading to memory leak Product: glibc Version: 2.26 Status: UNCONFIRMED Severity: normal Priority: P2 Component: malloc Assignee: unassigned at sourceware dot org Reporter: wangxuszcn at foxmail dot com Target Milestone: --- The malloc function in the GNU C Library (aka glibc or libc6) since 2.26, may return a memory block which contain another valid memory block pointer, potentially leading to memory leak. This occurs because the function tcache_get() of per-thread cache (aka tcache) feature does not set e->next = NULL. patche canbe: @@ -2936,6 +3074,7 @@ tcache_get (size_t tc_idx) tcache->entries[tc_idx] = e->next; --(tcache->counts[tc_idx]); e->key = NULL; + e->next = NULL; return (void *) e; } BTW,can we request a CVE? -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2020-05-08 3:35 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-08 3:35 wangxuszcn at foxmail dot com [this message] 2020-05-08 9:51 ` [Bug malloc/25945] " wangxuszcn at foxmail dot com 2020-05-08 12:48 ` [Bug malloc/25945] memory block return by tcache_get() may contain anather valid memory block pointer, leading to information disclosure wangxuszcn at foxmail dot com 2020-05-08 13:03 ` wangxuszcn at foxmail dot com 2020-05-08 16:19 ` carlos at redhat dot com 2020-05-08 16:20 ` [Bug malloc/25945] ASLR information leak via Safe-Linking and tcache or fastbin chunks carlos at redhat dot com 2020-05-08 16:20 ` fweimer at redhat dot com 2020-05-08 16:23 ` fweimer at redhat dot com 2020-05-08 16:44 ` carlos at redhat dot com 2020-05-08 19:18 ` dj at redhat dot com 2020-05-09 3:40 ` wangxuszcn at foxmail dot com 2020-05-09 3:45 ` wangxuszcn at foxmail dot com 2020-05-13 15:22 ` carlos at redhat dot com 2020-05-15 2:04 ` wangxuszcn at foxmail dot com 2020-05-15 6:44 ` wangxuszcn at foxmail dot com
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-25945-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: linkBe 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).