From: "Serge E. Hallyn" <serge@hallyn.com>
To: Kees Cook <keescook@chromium.org>
Cc: linux-kernel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>,
Oleg Nesterov <oleg@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Serge Hallyn <serge.hallyn@canonical.com>,
PaX Team <pageexec@freemail.hu>, Emese Revfy <re.emese@gmail.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] signal: stop info leak via the tkill and the tgkill syscalls
Date: Sat, 20 Apr 2013 17:14:42 -0500 [thread overview]
Message-ID: <20130420221442.GB25043@austin.hallyn.com> (raw)
In-Reply-To: <1366226365-15594-1-git-send-email-keescook@chromium.org>
Quoting Kees Cook (keescook@chromium.org):
> From: Emese Revfy <re.emese@gmail.com>
>
> This fixes a kernel memory contents leak via the tkill and tgkill syscalls
> for compat processes.
>
> This is visible in the siginfo_t->_sifields._rt.si_sigval.sival_ptr field
> when handling signals delivered from tkill.
>
> The place of the infoleak:
>
> int copy_siginfo_to_user32(compat_siginfo_t __user *to, siginfo_t *from)
> {
> ...
> put_user_ex(ptr_to_compat(from->si_ptr), &to->si_ptr);
> ...
> }
>
> Signed-off-by: Emese Revfy <re.emese@gmail.com>
Sorry, not sure if this is applied yet,
Acked-by: Serge Hallyn <serge.hallyn@canonical.com>
> Reviewed-by: PaX Team <pageexec@freemail.hu>
> Signed-off-by: Kees Cook <keescook@chromium.org>
> Cc: stable@vger.kernel.org
> ---
> kernel/signal.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/signal.c b/kernel/signal.c
> index dd72567..598dc06 100644
> --- a/kernel/signal.c
> +++ b/kernel/signal.c
> @@ -2948,7 +2948,7 @@ do_send_specific(pid_t tgid, pid_t pid, int sig, struct siginfo *info)
>
> static int do_tkill(pid_t tgid, pid_t pid, int sig)
> {
> - struct siginfo info;
> + struct siginfo info = {};
>
> info.si_signo = sig;
> info.si_errno = 0;
> --
> 1.7.9.5
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2013-04-20 22:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 19:19 Kees Cook
2013-04-20 22:14 ` Serge E. Hallyn [this message]
2013-04-20 22:29 ` Eric W. Biederman
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=20130420221442.GB25043@austin.hallyn.com \
--to=serge@hallyn.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=pageexec@freemail.hu \
--cc=re.emese@gmail.com \
--cc=serge.hallyn@canonical.com \
--cc=stable@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®