From: Chris Wright <chrisw@osdl.org>
To: Ken Ashcraft <ken@coverity.com>
Cc: linux-kernel@vger.kernel.org, mc@cs.stanford.edu,
linux@3ware.com, James.Bottomley@steeleye.com
Subject: Re: [CHECKER] Probable security holes in 2.6.5
Date: Fri, 16 Apr 2004 17:16:28 -0700 [thread overview]
Message-ID: <20040416171628.F22989@build.pdx.osdl.net> (raw)
In-Reply-To: <1082134916.19301.7.camel@dns.coverity.int>; from ken@coverity.com on Fri, Apr 16, 2004 at 10:01:57AM -0700
> [BUG]
> /home/kash/linux/linux-2.6.5/drivers/scsi/3w-xxxx.c:780:tw_chrdev_ioctl:
> ERROR:TAINT: 673:780:Passing unbounded user value "((1025 +
> (*tw_ioctl).data_buffer_length) - 1)" as arg 2 to function
> "copy_to_user", which uses it unsafely in model
> [SOURCE_MODEL=(lib,copy_from_user,user,taintscalar)]
> [SINK_MODEL=(lib,copy_to_user,user,trustingsink)] [PATH= "error != 0"
> on line 674 is false]
> }
>
> tw_ioctl = (TW_New_Ioctl *)cpu_addr;
>
> /* Now copy down the entire ioctl */
> Start --->
> error = copy_from_user(tw_ioctl, (void *)arg, data_buffer_length +
> sizeof(TW_New_Ioctl) - 1);
>
> ... DELETED 101 lines ...
>
> retval = -ENOTTY;
> goto out2;
> }
>
> /* Now copy the response to userspace */
> Error --->
> error = copy_to_user((void *)arg, tw_ioctl, sizeof(TW_New_Ioctl) +
> tw_ioctl->data_buffer_length - 1);
> if (error == 0)
> retval = 0;
> out2:
The data_buffer_length was validated once, however upon second copy
it's conceivable it could've been maliciously changed, so just use
validated one. Patch below.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
===== drivers/scsi/3w-xxxx.c 1.40 vs edited =====
--- 1.40/drivers/scsi/3w-xxxx.c Tue Sep 23 08:00:30 2003
+++ edited/drivers/scsi/3w-xxxx.c Fri Apr 16 14:48:24 2004
@@ -683,7 +683,7 @@
break;
case TW_OP_AEN_LISTEN:
dprintk(KERN_WARNING "3w-xxxx: tw_chrdev_ioctl(): caught TW_AEN_LISTEN.\n");
- memset(tw_ioctl->data_buffer, 0, tw_ioctl->data_buffer_length);
+ memset(tw_ioctl->data_buffer, 0, data_buffer_length);
spin_lock_irqsave(tw_dev->host->host_lock, flags);
if (tw_dev->aen_head == tw_dev->aen_tail) {
@@ -777,7 +777,7 @@
}
/* Now copy the response to userspace */
- error = copy_to_user((void *)arg, tw_ioctl, sizeof(TW_New_Ioctl) + tw_ioctl->data_buffer_length - 1);
+ error = copy_to_user((void *)arg, tw_ioctl, sizeof(TW_New_Ioctl) + data_buffer_length - 1);
if (error == 0)
retval = 0;
out2:
next prev parent reply other threads:[~2004-04-17 0:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 17:01 Ken Ashcraft
2004-04-16 18:20 ` Chris Wright
2004-04-16 19:20 ` Jeff Garzik
2004-04-16 22:12 ` Chris Wright
2004-04-19 16:46 ` Jeff Garzik
2004-04-16 18:32 ` Chris Wright
2004-04-16 18:54 ` Chris Wright
2004-04-21 1:34 ` Andrea Arcangeli
2004-04-21 1:38 ` Chris Wright
2004-04-16 19:19 ` Chris Wright
2004-04-16 19:27 ` Chris Wright
2004-04-17 6:15 ` Rusty Russell
2004-04-16 20:02 ` Chris Wright
2004-04-16 20:23 ` Chris Wright
2004-04-17 0:16 ` Chris Wright [this message]
2004-04-17 1:00 ` Chris Wright
2004-04-19 16:27 ` Jeff Garzik
2004-04-19 19:09 ` Chris Wright
2004-04-19 20:38 ` Chris Wright
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=20040416171628.F22989@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=James.Bottomley@steeleye.com \
--cc=ken@coverity.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@3ware.com \
--cc=mc@cs.stanford.edu \
/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
all inboxes | Powered by JetHome®