From: Chris Wright <chrisw@osdl.org>
To: Ken Ashcraft <ken@coverity.com>
Cc: linux-kernel@vger.kernel.org, mc@cs.stanford.edu,
james.bottomley@steeleye.com
Subject: Re: [CHECKER] Probable security holes in 2.6.5
Date: Fri, 16 Apr 2004 13:23:51 -0700 [thread overview]
Message-ID: <20040416132351.B22989@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] probably
> /home/kash/linux/linux-2.6.5/drivers/message/fusion/mptctl.c:2704:mptctl_hp_targetinfo: ERROR:TAINT: 2597:2704:Using user value "((karg).hdr).id" without first performing bounds checks [SOURCE_MODEL=(lib,copy_from_user,user,taintscalar)] [PATH= "pg0_alloc != 0" on line 2626 is false => "(*(*ioc).sh).host_no != ((karg).hdr).host" on line 2619 is false => "(*ioc).sh == 0" on line 2616 is false => "((*ioc).spi_data).sdp0length == 0" on line 2616 is false => "(*ioc).chip_type <= 2345" on line 2613 is false => "ioc == 0" on line 2604 is false => "iocnum = mpt_verify_adapter < 0" on line 2604 is false => "copy_from_user != 0" on line 2597 is false]
> CONFIGPARMS cfg;
> ConfigPageHeader_t hdr;
> int tmp, np, rc = 0;
>
> dctlprintk((": mptctl_hp_targetinfo called.\n"));
> Start --->
> if (copy_from_user(&karg, uarg, sizeof(hp_target_info_t))) {
>
> ... DELETED 101 lines ...
>
> pci_free_consistent(ioc->pcidev, data_sz, (u8 *) pg3_alloc,
> page_dma);
> }
> }
> hd = (MPT_SCSI_HOST *) ioc->sh->hostdata;
> if (hd != NULL)
> Error --->
> karg.select_timeouts = hd->sel_timeout[karg.hdr.id];
>
> /* Copy the data from kernel memory to user memory
> */
Yup. Looks like it's intended to be just 8 bits, considering:
cfg.pageAddr = (karg.hdr.channel << 8) | karg.hdr.id;
And it indexes into an array sized by:
#define MPT_MAX_FC_DEVICES 255
Patch below sanity checks id.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
===== drivers/message/fusion/mptctl.c 1.20 vs edited =====
--- 1.20/drivers/message/fusion/mptctl.c Sat Mar 27 07:38:07 2004
+++ edited/drivers/message/fusion/mptctl.c Fri Apr 16 13:20:33 2004
@@ -2608,6 +2608,9 @@
return -ENODEV;
}
+ if (karg.hdr.id >= MPT_MAX_FC_DEVICES)
+ return -EINVAL;
+
/* There is nothing to do for FCP parts.
*/
if ((int) ioc->chip_type <= (int) FC929)
next prev parent reply other threads:[~2004-04-16 20:24 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 [this message]
2004-04-17 0:16 ` Chris Wright
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=20040416132351.B22989@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=james.bottomley@steeleye.com \
--cc=ken@coverity.com \
--cc=linux-kernel@vger.kernel.org \
--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®