From: "Robert T. Johnson" <rtjohnso@eecs.berkeley.edu>
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: Markus.Lidel@shadowconnect.com,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: PATCH: 2.6.7-rc3 drivers/message/i2o/i2o_config.c: user/kernel pointer bugs
Date: 09 Jun 2004 21:03:04 -0700 [thread overview]
Message-ID: <1086840185.32058.351.camel@dooby.cs.berkeley.edu> (raw)
In-Reply-To: <20040610013734.GZ12308@parcelfarce.linux.theplanet.co.uk>
On Wed, 2004-06-09 at 18:37, viro@parcelfarce.linux.theplanet.co.uk
wrote:
> On Wed, Jun 09, 2004 at 04:01:02PM -0700, Robert T. Johnson wrote:
> > QUESTION: Does ioctl_passthru mean arg is a kernel pointer? If so, then
> > disregard this bug report.
>
> No - we have ->ioctl [== cfg_ioctl()] -> ioctl_passthru() chain in there,
> so at the very least it can get arbitrary pointers straight from userland.
Thanks.
> > + if (copy_from_user(&cmd, (void *)arg, sizeof(cmd)))
> > + return -EFAULT;
>
> Fix the indentation, please.
Whoops. Thanks. Done.
> > - memset(&msg, 0, MSG_FRAME_SIZE*4);
> > + memset(msg, 0, MSG_FRAME_SIZE*4);
> > - memset(&msg, 0, MSG_FRAME_SIZE*4);
> > + memset(msg, 0, MSG_FRAME_SIZE*4);
These fix false positives in cqual -- it's picky about conversions
between arrays and pointers. I left them out of the revised patch, but
if I submitted a patch for a bunch of little things like this, would it
be accepted? I described some scenarios in an old email where &array
can cause problems:
http://lkml.org/lkml/2004/2/23/233
The bug I just found in ipmi_devintf.c is probably an example of exactly
this kind of problem.
Best,
Rob
--- linux-2.6.7-rc3-full/drivers/message/i2o/i2o_config.c.orig Wed Jun 9 12:14:08 2004
+++ linux-2.6.7-rc3-full/drivers/message/i2o/i2o_config.c Wed Jun 9 20:53:01 2004
@@ -842,10 +842,10 @@ static int ioctl_evt_get(unsigned long a
static int ioctl_passthru(unsigned long arg)
{
- struct i2o_cmd_passthru *cmd = (struct i2o_cmd_passthru *) arg;
+ struct i2o_cmd_passthru cmd;
struct i2o_controller *c;
u32 msg[MSG_FRAME_SIZE];
- u32 *user_msg = (u32*)cmd->msg;
+ u32 *user_msg;
u32 *reply = NULL;
u32 *user_reply = NULL;
u32 size = 0;
@@ -858,7 +858,12 @@ static int ioctl_passthru(unsigned long
u32 i = 0;
ulong p = 0;
- c = i2o_find_controller(cmd->iop);
+ if (copy_from_user(&cmd, (void *)arg, sizeof(cmd)))
+ return -EFAULT;
+
+ user_msg = cmd.msg;
+
+ c = i2o_find_controller(cmd.iop);
if(!c)
return -ENXIO;
next prev parent reply other threads:[~2004-06-10 4:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 23:01 PATCH: 2.6.7-rc3 drivers/message/i2o/i2o_config.c: user/kernel pointer bugs Robert T. Johnson
2004-06-10 1:37 ` viro
2004-06-10 4:03 ` Robert T. Johnson [this message]
2004-06-11 6:24 ` Markus Lidel
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=1086840185.32058.351.camel@dooby.cs.berkeley.edu \
--to=rtjohnso@eecs.berkeley.edu \
--cc=Markus.Lidel@shadowconnect.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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