From: Jiri Slaby <jslaby@suse.cz>
To: Vasiliy Kulikov <segooon@gmail.com>
Cc: kernel-janitors@vger.kernel.org,
Greg Kroah-Hartman <gregkh@suse.de>,
Alan Cox <alan@linux.intel.com>, Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/8] char: synclink: fix information leak to userland
Date: Sun, 17 Oct 2010 17:46:15 +0000 [thread overview]
Message-ID: <4CBB3667.2010804@suse.cz> (raw)
In-Reply-To: <20101017153839.GA11029@albatros>
On 10/17/2010 05:38 PM, Vasiliy Kulikov wrote:
> On Sun, Oct 17, 2010 at 17:34 +0200, Jiri Slaby wrote:
>> On 10/17/2010 04:41 PM, Vasiliy Kulikov wrote:
>>> Structure new_line is copied to userland with some padding fields unitialized.
>>> It leads to leaking of stack memory.
>>
>> I think your tool has a bug. I must admit I fail to see the padding
>> which would cause leaks. Could you elaborate?
>
> I didn't use any tool except "grep copy_to_user" :)
>
> typedef struct {
> unsigned int clock_rate; /* bits per second */
> unsigned int clock_type; /* internal, external, TX-internal etc. */
> unsigned short loopback;
> } sync_serial_settings; /* V.35, V.24, X.21 */
>
> On x86_64 sizeof(sync_serial_settings) = 4 + 4 + 2 + 2 = 12.
> The last 2 is padding.
Ah, good to know that even end of structures is padded.
thanks for clarification,
--
js
suse labs
next prev parent reply other threads:[~2010-10-17 17:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-17 14:41 [PATCH 6/8] char: synclink: fix information leak to userland Vasiliy Kulikov
2010-10-17 15:34 ` Jiri Slaby
2010-10-17 15:38 ` Vasiliy Kulikov
2010-10-17 17:36 ` Dan Carpenter
2010-10-17 17:50 ` Vasiliy Kulikov
2010-10-17 17:46 ` Jiri Slaby [this message]
2010-10-17 17:55 ` Vasiliy Kulikov
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=4CBB3667.2010804@suse.cz \
--to=jslaby@suse.cz \
--cc=alan@linux.intel.com \
--cc=arnd@arndb.de \
--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