From: Steve Dickson <SteveD@redhat.com>
To: Steve Dickson <steved@redhat.com>
Cc: Libtirpc-devel Mailing List
<libtirpc-devel@lists.sourceforge.net>,
Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [Libtirpc-devel] [PATCH] svc_getargs(): Should not be freeing arg pointers on failures
Date: Mon, 22 Apr 2013 08:18:16 -0400 [thread overview]
Message-ID: <51752A88.4080301@RedHat.com> (raw)
In-Reply-To: <1366310898-9206-1-git-send-email-steved@redhat.com>
On 18/04/13 14:48, Steve Dickson wrote:
> commit 82cc2e61 (SVCAUTH_WRAP/SVCAUTH_UNWRAP) introduce a regression
> that causes callers of svc_getargs() to crash when svc_freeargs() frees
> args points that are allocated on the stack.
>
> svc_getargs() should let the callers do the freeing and not make any
> assumptions on the type of memory passed in.
>
> Also see:
> https://bugzilla.redhat.com/show_bug.cgi?id=948378
> and
> CVE-2013-1950 EMBARGOED rpcbind: invalid pointer free leads to crash
>
> Signed-off-by: Steve Dickson <steved@redhat.com>
Committed...
steved.
> ---
> src/svc_dg.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/src/svc_dg.c b/src/svc_dg.c
> index b1ac462..6e00191 100644
> --- a/src/svc_dg.c
> +++ b/src/svc_dg.c
> @@ -284,7 +284,6 @@ svc_dg_getargs(xprt, xdr_args, args_ptr)
> {
> if (! SVCAUTH_UNWRAP(xprt->xp_auth, &(su_data(xprt)->su_xdrs),
> xdr_args, args_ptr)) {
> - (void)svc_freeargs(xprt, xdr_args, args_ptr);
> return FALSE;
> }
> return TRUE;
>
prev parent reply other threads:[~2013-04-22 12:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 18:48 [PATCH] svc_getargs(): Should not be freeing arg pointers on failures Steve Dickson
2013-04-22 12:18 ` Steve Dickson [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=51752A88.4080301@RedHat.com \
--to=steved@redhat.com \
--cc=libtirpc-devel@lists.sourceforge.net \
--cc=linux-nfs@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.