public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug malloc/15857] posix_memalign / memalign integer overflow can corrupt allocator state Date: Tue, 20 Aug 2013 09:16:00 -0000 [thread overview] Message-ID: <bug-15857-131-0KO1l2D5gQ@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15857-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=15857 Florian Weimer <fweimer at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fweimer at redhat dot com -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2013-08-20 9:16 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-08-20 8:03 [Bug malloc/15857] New: " will.newton at gmail dot com 2013-08-20 9:16 ` fweimer at redhat dot com [this message] 2013-09-11 9:50 ` [Bug malloc/15857] " will.newton at gmail dot com 2013-10-25 14:00 ` cvs-commit at gcc dot gnu.org 2013-11-01 19:01 ` cvs-commit at gcc dot gnu.org 2013-11-21 17:14 ` cvs-commit at gcc dot gnu.org 2014-01-06 16:55 ` cvs-commit at gcc dot gnu.org 2014-01-06 16:56 ` cvs-commit at gcc dot gnu.org 2014-06-13 9:44 ` fweimer at redhat dot com 2015-01-16 16:59 ` cvs-commit at gcc dot gnu.org 2015-01-29 18:48 ` cvs-commit at gcc dot gnu.org 2015-02-23 15:02 ` cvs-commit at gcc dot gnu.org 2015-02-24 10:54 ` [Bug malloc/15857] posix_memalign / memalign integer overflow can corrupt allocator state (CVE-2013-4332) fweimer at redhat 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-15857-131-0KO1l2D5gQ@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).