mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: Ken Ashcraft <ken@coverity.com>
Cc: linux-kernel@vger.kernel.org, mc@cs.stanford.edu, rusty@rustcorp.com.au
Subject: Re: [CHECKER] Probable security holes in 2.6.5
Date: Fri, 16 Apr 2004 12:27:33 -0700	[thread overview]
Message-ID: <20040416122733.Z22989@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/kernel/module.c:1303:load_module:
> ERROR:TAINT: 1283:1303:Using user value "((*hdr).e_shstrndx * 0)"
> without first performing bounds checks
> [SOURCE_MODEL=(lib,copy_from_user,user,taintscalar)] [PATH=]    
> 
> 	/* Suck in entire file: we'll want most of it. */
> 	/* vmalloc barfs on "unusual" numbers.  Check here */
> 	if (len > 64 * 1024 * 1024 || (hdr = vmalloc(len)) == NULL)
> 		return ERR_PTR(-ENOMEM);
> Start --->
> 	if (copy_from_user(hdr, umod, len) != 0) {
> 
> 	... DELETED 14 lines ...
> 
> 	if (len < hdr->e_shoff + hdr->e_shnum * sizeof(Elf_Shdr))
> 		goto truncated;
> 
> 	/* Convenience variables */
> 	sechdrs = (void *)hdr + hdr->e_shoff;
> Error --->
> 	secstrings = (void *)hdr + sechdrs[hdr->e_shstrndx].sh_offset;
> 	sechdrs[0].sh_addr = 0;
> 
> 	/* And these should exist, but gcc whinges if we don't init them */

Loading modules is inherently risky.  I'm not sure how much we want to
worry about malicious elf headers when loading a module...you've already
given away the family jewels ;-)

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

  parent reply	other threads:[~2004-04-16 19:27 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 [this message]
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
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=20040416122733.Z22989@build.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=ken@coverity.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mc@cs.stanford.edu \
    --cc=rusty@rustcorp.com.au \
    /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®