From: Rusty Russell <rusty@rustcorp.com.au>
To: Chris Wright <chrisw@osdl.org>
Cc: Ken Ashcraft <ken@coverity.com>,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
mc@cs.stanford.edu
Subject: Re: [CHECKER] Probable security holes in 2.6.5
Date: Sat, 17 Apr 2004 16:15:44 +1000 [thread overview]
Message-ID: <1082181408.2122.106.camel@bach> (raw)
In-Reply-To: <20040416122733.Z22989@build.pdx.osdl.net>
On Sat, 2004-04-17 at 05:27, Chris Wright wrote:
> > [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
Yes, this is a special case. We've already checked CAP_SYS_MODULE, and
we only do trivial sanity checks for correct arch and truncated
modules. This is by policy, since there are things we simply can't
check (like the code we're about to run!),
Hope that helps!
Rusty.
--
Anyone who quotes me in their signature is an idiot -- Rusty Russell
next prev parent reply other threads:[~2004-04-17 6:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 17:01 [CHECKER] Probable security holes in 2.6.5 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 [this message]
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=1082181408.2122.106.camel@bach \
--to=rusty@rustcorp.com.au \
--cc=chrisw@osdl.org \
--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