From: Michael Buesch <mb@bu3sch.de>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: David Wagner <daw-usenet@taverner.cs.berkeley.edu>,
linux-kernel@vger.kernel.org
Subject: Re: Really good idea to allow mmap(0, FIXED)?
Date: Sun, 8 Oct 2006 21:18:29 +0200 [thread overview]
Message-ID: <200610082118.29200.mb@bu3sch.de> (raw)
In-Reply-To: <452844AB.2050406@goop.org>
On Sunday 08 October 2006 02:22, Jeremy Fitzhardinge wrote:
> Though (*something_ops->thingy)() becomes a lot more interesting if
> something_ops or ->thingy is NULL...
It's always very critical if a userspace program can modify some
data in the kernel. Be it function pointers or plain data.
Also consider something like:
if (task->uid == 0)
allow_access_to_time_machine();
else
return -EPERM;
Now if "task" may be a NULL pointer (due to a bug) it
can be exploited.
PS: Please don't drop me from the CC list ;)
--
Greetings Michael.
next prev parent reply other threads:[~2006-10-08 19:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 18:59 Really good idea to allow mmap(0, FIXED)? Michael Buesch
2006-10-05 19:50 ` linux-os (Dick Johnson)
2006-10-06 14:40 ` Michael Buesch
2006-10-05 21:58 ` Alan Cox
2006-10-06 14:44 ` Michael Buesch
2006-10-07 11:23 ` Pavel Machek
2006-10-05 23:55 ` David Wagner
2006-10-06 4:34 ` Jeremy Fitzhardinge
2006-10-06 5:39 ` Jan Engelhardt
2006-10-06 19:47 ` David Wagner
2006-10-06 7:25 ` Arjan van de Ven
2006-10-06 10:36 ` Mikael Pettersson
2006-10-06 11:20 ` Arjan van de Ven
2006-10-06 19:43 ` David Wagner
2006-10-08 0:22 ` Jeremy Fitzhardinge
2006-10-08 2:03 ` David Wagner
2006-10-08 19:18 ` Michael Buesch [this message]
2006-10-06 14:55 ` Michael Buesch
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=200610082118.29200.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=daw-usenet@taverner.cs.berkeley.edu \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.