public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "jeremy.bennett at embecosm dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug server/15236] New: gdbserver write to linux memory with zero length corrupts stack Date: Wed, 06 Mar 2013 15:02:00 -0000 [thread overview] Message-ID: <bug-15236-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=15236 Bug #: 15236 Summary: gdbserver write to linux memory with zero length corrupts stack Product: gdb Version: unknown Status: NEW Severity: normal Priority: P2 Component: server AssignedTo: unassigned@sourceware.org ReportedBy: jeremy.bennett@embecosm.com Classification: Unclassified The function linux_write_memory () allocates a buffer on the stack to hold a copy of the data to be written. register PTRACE_XFER_TYPE *buffer = (PTRACE_XFER_TYPE *) alloca (count * sizeof (PTRACE_XFER_TYPE)); "count" is the number of bytes to be written, rounded up to the nearest multiple of sizeof (PTRACE_XFER_TYPE). I.e. sizeof (long). It later uses buffer[0] = ptrace (PTRACE_PEEKTEXT, pid, (PTRACE_ARG3_TYPE) (uintptr_t) addr, 0); The problem is that this function can be called to write zero bytes, for example when receiving an X packet of length 0 (used to test if 8-bit write is supported). Under these circumstances, count can be zero. Since in this case, buffer[0] may never have been allocated, the stack is corrupted. Patch to follow... -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2013-03-06 15:02 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-06 15:02 jeremy.bennett at embecosm dot com [this message] 2013-03-06 15:03 ` [Bug server/15236] " jeremy.bennett at embecosm dot com 2013-03-06 15:42 ` jeremy.bennett at embecosm dot com 2013-03-06 16:45 ` tromey at redhat dot com 2013-03-06 18:04 ` jeremy.bennett at embecosm dot com 2013-03-07 9:48 ` cvs-commit at gcc dot gnu.org 2013-03-07 9:57 ` palves 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-15236-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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).