mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Freeing the ai_canonname in the getaddrinfo directly leads to a Segmentation fault
Date: Sun, 17 Feb 2019 11:00:01 -0500	[thread overview]
Message-ID: <20190217160001.GF23599@brightrain.aerifal.cx> (raw)
In-Reply-To: <20190217155531.31d2d938@onion.lan>

On Sun, Feb 17, 2019 at 03:55:31PM +0100, Peter Wagner wrote:
> Hello,
> 
> after the latest update to musl 1.1.21 this code compiles on glibc
> without a problem and works. It compiles for musl too but it crashes at
> the free.
> 
> #include <stdlib.h>
> #include <sys/types.h>
> #include <sys/socket.h>
> #include <netdb.h>
> 
> int main(){
>         int error;
>         const char *paddr = "192.168.1.1";
>         struct addrinfo *ai = NULL;
> 
>         struct addrinfo hint = {
>                 /* don't return duplicates */
>                 .ai_protocol    = (int)IPPROTO_UDP,
>                 .ai_flags       = AI_NUMERICHOST,
>                 .ai_family      = AF_UNSPEC,
>         };
> 
>         error = getaddrinfo(paddr, NULL, &hint, &ai);
> 
>         if ( ! error )
>         {
>                 free(ai->ai_canonname); /* crashes here*/
>         }
> }
> 
> 
> The gdb backtrace:
> 
> (gdb) c
> Continuing.
> 
> Program received signal SIGSEGV, Segmentation fault.
> __bin_chunk (self=0x77ffffbc) at src/malloc/malloc.c:450
> 450             if (next->psize != self->csize) a_crash();
> (gdb) bt
> #0  __bin_chunk (self=0x77ffffbc) at src/malloc/malloc.c:450
> #1  0x004006b0 in main () at foo.c:22
> 
> 
> The corresponding code in malloc.c:
> 
>    │449  /* Crash on corrupted footer (likely from buffer overflow)   */
> │ >│450   if (next->psize != self->csize) a_crash(); 
> 
> Shouldn't it be possible to free a part of a structure instead of
> freeing the addrinfo structure ai points to as a whole?

No. Short of an explicit contract that you can, the assumption is that
you can't. Nothing says that ai_canonname points to memory "as if
obtained by malloc", or that it can be passed to free. In fact the
spec even allows it to point to the same storage as the host argument.
The relevant text is:

    "If nodename is not null, and if requested by the AI_CANONNAME
    flag, the ai_canonname field of the first returned addrinfo
    structure shall point to a null-terminated string containing the
    canonical name corresponding to the input nodename; if the
    canonical name is not available, then ai_canonname shall refer to
    the nodename argument or a string with the same contents."

Code passing this to free is just buggy.

Rich


      reply	other threads:[~2019-02-17 16:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-17 14:55 Peter Wagner
2019-02-17 16:00 ` Rich Felker [this message]

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=20190217160001.GF23599@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).