From: Paul Fulghum <paulkf@microgate.com>
To: Vasiliy Kulikov <segooon@gmail.com>
Cc: kernel-janitors@vger.kernel.org,
Greg Kroah-Hartman <gregkh@suse.de>,
Alan Cox <alan@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 7/8] char: synclink_gt: fix information leak to userland
Date: Mon, 18 Oct 2010 15:10:18 -0600 [thread overview]
Message-ID: <4CBCB7BA.5080601@microgate.com> (raw)
In-Reply-To: <1287326496-8178-1-git-send-email-segooon@gmail.com>
Acked-by: Paul Fulghum <paulkf@microgate.com>
On 10/17/2010 8:41 AM, Vasiliy Kulikov wrote:
> Structures tmp_params and new_line are copied to userland with some padding
> fields unitialized. It leads to leaking of stack memory.
>
> Signed-off-by: Vasiliy Kulikov <segooon@gmail.com>
--
Paul Fulghum
MicroGate Systems, Ltd.
=Customer Driven, by Design=
(800)444-1982
(512)345-7791 (Direct)
(512)343-9046 (Fax)
Central Time Zone (GMT -6h)
www.microgate.com
prev parent reply other threads:[~2010-10-18 20:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-17 14:41 [PATCH 7/8] char: synclink_gt: fix information leak to userland Vasiliy Kulikov
2010-10-18 21:10 ` Paul Fulghum [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=4CBCB7BA.5080601@microgate.com \
--to=paulkf@microgate.com \
--cc=akpm@linux-foundation.org \
--cc=alan@linux.intel.com \
--cc=gregkh@suse.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=segooon@gmail.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox