From: Eugene Kapun <abacabadabacaba@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Does tkill/tgkill leak info from kernel stack?
Date: Wed, 06 Jan 2010 03:20:35 +0300 [thread overview]
Message-ID: <4B43D753.90909@gmail.com> (raw)
As I can see, tkill and tgkill syscalls call do_tkill (kernel/signal.c:2336).
This function doesn't clear info struct, so it would contain what was on kernel
stack previously. And because SI_TKILL < 0, precautions in copy_siginfo_to_user
(kernel/signal.c:2154) won't prevent this data from going to userspace. Is it a
bug?
reply other threads:[~2010-01-06 0:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4B43D753.90909@gmail.com \
--to=abacabadabacaba@gmail.com \
--cc=linux-kernel@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.