public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: daw@cs.berkeley.edu (David Wagner)
To: linux-kernel@vger.kernel.org
Subject: Re: Really good idea to allow mmap(0, FIXED)?
Date: Fri, 6 Oct 2006 19:47:41 +0000 (UTC)	[thread overview]
Message-ID: <eg6bst$7r1$2@taverner.cs.berkeley.edu> (raw)
In-Reply-To: Pine.LNX.4.61.0610060739520.12702@yvahk01.tjqt.qr

Jan Engelhardt  wrote:
>For reference, please see http://lkml.org/lkml/2006/2/22/90

Thanks.  Ok, I've read that.  That was helpful.  But I think this risk
is more serious than was realized in that thread from February.

The February thread you mention talked about the security consequences of
calling (dereferencing) a function pointer that is NULL.  The security
consequences are indeed bad.  However, that thread only discussed the
security consequences of NULL pointer bugs involving function pointers,
and there was no indication in that thread that other types of NULL
pointer bugs had any security relevance.

But now it seems, as I described in my email, that all NULL pointer bugs
(whether function pointers or not) have the potential to create security
vulnerabilities.  Every NULL pointer bug has to be viewed with suspicion,
until it has been confirmed that it cannot be exploited.  This sounds more
serious than was realized back in February.

Right?  Or am I missing something important again?

  reply	other threads:[~2006-10-06 19:47 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 [this message]
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
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='eg6bst$7r1$2@taverner.cs.berkeley.edu' \
    --to=daw@cs.berkeley.edu \
    --cc=daw-usenet@taverner.cs.berkeley.edu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox