mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dawson Engler <engler@csl.Stanford.EDU>
To: davem@redhat.com (David S. Miller)
Cc: linux-kernel@vger.kernel.org
Subject: Re: [CHECKER] 4 security holes in 2.4.4-ac8
Date: Tue, 29 May 2001 15:57:53 -0700 (PDT)	[thread overview]
Message-ID: <200105292257.PAA00192@csl.Stanford.EDU> (raw)
In-Reply-To: <15124.7615.678503.824814@pizda.ninka.net> from "David S. Miller" at May 29, 2001 03:07:59 PM

>  > [BUG] raddr seems to be a user pointer, but is written at the end of
>  >       the system call.
>  > 
>  > ipc/shm.c: ERROR: system call 'sys_shmat' derefs non-tainted param= 3
>  > 
>  > asmlinkage long sys_shmat (int shmid, char *shmaddr, int shmflg, ulong *raddr)
>  > {
>  >         struct shmid_kernel *shp;
>  > 
>  > 
>  > 	...
>  >         *raddr = (unsigned long) user_addr;
>  >         err = 0;
>  >         if (IS_ERR(user_addr))
>  >                 err = PTR_ERR(user_addr);
>  >         return err;
> 
> Believe it or not, this one is OK :-)
> 
> All callers pass in a pointer to a local stack kernel variable
> in raddr.

Ah.  I assumed that "sys_*" meant that all pointers were from user space ---
is this generally not the case?  (Also, are there other functions called 
directly from user space that don't have the sys_* prefix?)

  reply	other threads:[~2001-05-29 22:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-29 22:00 Dawson Engler
2001-05-29 22:07 ` David S. Miller
2001-05-29 22:57   ` Dawson Engler [this message]
2001-05-30  5:48     ` Ingo Molnar
2001-05-29 23:00   ` David S. Miller
2001-05-29 23:16     ` Dawson Engler
2001-05-29 23:33       ` Jeff Garzik
2001-05-29 23:28     ` David S. Miller
2001-05-30 17:27 ` Greg KH
     [not found] <15124.10785.10143.242660@pizda.ninka.net.suse.lists.linux.kernel>
     [not found] ` <200105292316.QAA00305@csl.Stanford.EDU.suse.lists.linux.kernel>
     [not found]   ` <15124.12421.609194.476097@pizda.ninka.net.suse.lists.linux.kernel>
2001-05-30  9:38     ` Andi Kleen
2001-05-30 10:33       ` Keith Owens

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=200105292257.PAA00192@csl.Stanford.EDU \
    --to=engler@csl.stanford.edu \
    --cc=davem@redhat.com \
    --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

all inboxes | Powered by JetHome®