From: Greg KH <greg@kroah.com>
To: Jiri Kosina <jkosina@suse.cz>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
randy.dunlap@oracle.com, joe@perches.com
Subject: Re: [Oops 1/2]Something wrong with copy_from_user() function
Date: Sat, 30 Apr 2011 19:39:53 -0700 [thread overview]
Message-ID: <20110501023953.GA30713@kroah.com> (raw)
In-Reply-To: <20110501012127.GA2378@gmail.com>
On Sun, May 01, 2011 at 09:21:30AM +0800, Harry Wei wrote:
> On Sat, Apr 30, 2011 at 11:13:10PM +0200, Jiri Kosina wrote:
> > On Sat, 30 Apr 2011, Harry Wei wrote:
> >
> >
> > wpa_set_keys() function (from staging drivers) in your kernel uses
> > copy_from_user() without proper bounds checking, and thus can overflow and
> > corrupt memory.
> Hmmm, i see.
Patches gladly welcome to fix this :)
prev parent reply other threads:[~2011-05-01 15:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-30 6:13 [Oops 1/2]Something wrong with copy_from_user() function Harry Wei
2011-04-30 12:41 ` Andy Lutomirski
2011-04-30 21:13 ` Jiri Kosina
2011-05-01 1:21 ` Harry Wei
2011-05-01 2:39 ` Greg KH [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=20110501023953.GA30713@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=jkosina@suse.cz \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.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