From: Chris Wright <chrisw@osdl.org>
To: blaisorblade@yahoo.it
Cc: stable@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [stable] [patch 1/1] sys_get_thread_area does not clear the returned argument
Date: Sat, 30 Jul 2005 22:17:49 -0700 [thread overview]
Message-ID: <20050731051749.GL19052@shell0.pdx.osdl.net> (raw)
In-Reply-To: <20050730190703.233BB843@zion.home.lan>
* blaisorblade@yahoo.it (blaisorblade@yahoo.it) wrote:
>
> From: Blaisorblade <blaisorblade@yahoo.it>
> CC: <stable@kernel.org>
>
> sys_get_thread_area does not memset to 0 its struct user_desc info before
> copying it to user space... since sizeof(struct user_desc) is 16 while the
> actual datas which are filled are only 12 bytes + 9 bits (across the
> bitfields), there is a (small) information leak.
>
> This was already committed to Linus' repository.
Thanks, queued to -stable.
-chris
prev parent reply other threads:[~2005-07-31 5:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-30 19:07 [patch 1/1] sys_get_thread_area does not clear the returned argument blaisorblade
2005-07-31 5:17 ` Chris Wright [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=20050731051749.GL19052@shell0.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=blaisorblade@yahoo.it \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox