From: Chris Wright <chrisw@sous-sol.org>
To: Eric Paris <eparis@redhat.com>
Cc: selinux@tycho.nsa.gov, sds@tycho.nsa.gov, drepper@redhat.com,
alan@redhat.com, roland@redhat.com, arjan@infradead.org,
mingo@elte.hu, viro@zeniv.linux.org.uk, jmorris@namei.org,
chrisw@redhat.com
Subject: Re: [PATCH] SELinux protection for exploiting null dereference using mmap
Date: Wed, 30 May 2007 18:40:57 -0700 [thread overview]
Message-ID: <20070531014057.GI3429@sequoia.sous-sol.org> (raw)
In-Reply-To: <1180561713.3633.27.camel@dhcp231-215.rdu.redhat.com>
* Eric Paris (eparis@redhat.com) wrote:
> + int (*mmap_zero) (void);
> int (*file_mmap) (struct file * file,
> unsigned long reqprot,
> unsigned long prot, unsigned long flags);
When I looked into this originally, I expected to use existing file_mmap
hook, augmented with addr (of course, adding smth for mremap as well).
> --- a/mm/mmap.c
> +++ b/mm/mmap.c
> @@ -1026,6 +1026,12 @@ unsigned long do_mmap_pgoff(struct file * file, unsigned long addr,
> error = security_file_mmap(file, reqprot, prot, flags);
> if (error)
> return error;
> +
> + if (unlikely(addr < PAGE_SIZE)) {
> + error = security_mmap_zero();
> + if (error)
> + return error;
> + }
I believe this is correct (despite the distinction of MAP_FIXED vs
!MAP_FIXED).
> --- a/mm/mremap.c
> +++ b/mm/mremap.c
> @@ -291,6 +291,12 @@ unsigned long do_mremap(unsigned long addr,
> if ((addr <= new_addr) && (addr+old_len) > new_addr)
> goto out;
>
> + if (unlikely(new_addr < PAGE_SIZE)) {
> + ret = security_mmap_zero();
> + if (ret)
> + goto out;
> + ret = -EINVAL;
> + }
This, on the other hand, I believe is correct only to the degree that
the current semantics of get_unmapped_area stay unchanged. This is why
I had expected passing the addr to the module directly, since the cutoff
point is a lot like policy (one page is somewhat arbitrary).
thanks,
-chris
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2007-05-31 1:40 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 21:48 [PATCH] SELinux protection for exploiting null dereference using mmap Eric Paris
2007-05-31 0:07 ` James Morris
2007-05-31 5:46 ` Eric Paris
2007-05-31 13:45 ` James Morris
2007-05-31 14:45 ` Stephen Smalley
[not found] ` <465EE1C9.3020809@redhat.com>
2007-05-31 15:07 ` Stephen Smalley
2007-05-31 15:19 ` James Morris
2007-05-31 15:31 ` Stephen Smalley
2007-06-02 2:27 ` Chris Wright
2007-05-31 1:40 ` Chris Wright [this message]
[not found] ` <20070603205653.GE25869@devserv.devel.redhat.com>
2007-06-04 13:38 ` Stephen Smalley
2007-06-05 20:34 ` [PATCH] Protection " Eric Paris
2007-06-05 20:34 ` Eric Paris
2007-06-05 21:00 ` James Morris
2007-06-05 21:00 ` James Morris
2007-06-05 21:16 ` Alan Cox
2007-06-05 21:28 ` Eric Paris
2007-06-05 21:28 ` Eric Paris
2007-06-05 22:46 ` H. Peter Anvin
2007-06-07 14:28 ` Pavel Machek
2007-06-06 12:47 ` Stephen Smalley
2007-06-06 12:47 ` Stephen Smalley
2007-06-07 16:58 ` Jan Engelhardt
2007-06-06 6:30 ` Eric Paris
2007-06-06 6:30 ` Eric Paris
2007-06-06 13:21 ` James Morris
2007-06-06 13:21 ` James Morris
2007-06-06 17:30 ` Stephen Smalley
2007-06-06 17:30 ` Stephen Smalley
2007-06-06 18:01 ` James Morris
2007-06-06 18:01 ` James Morris
2007-06-06 18:06 ` Chris Wright
2007-06-06 18:06 ` Chris Wright
2007-06-20 19:48 ` Adam Jackson
2007-06-05 22:49 ` Chris Wright
2007-06-05 22:49 ` Chris Wright
2007-06-05 22:53 ` Chris Wright
2007-06-05 22:53 ` Chris Wright
2007-06-06 12:12 ` Stephen Smalley
2007-06-06 12:12 ` Stephen Smalley
2007-06-06 9:01 ` Russell Coker
2007-06-06 9:01 ` Russell Coker
2007-06-06 12:18 ` Stephen Smalley
2007-06-06 12:18 ` Stephen Smalley
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=20070531014057.GI3429@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=alan@redhat.com \
--cc=arjan@infradead.org \
--cc=chrisw@redhat.com \
--cc=drepper@redhat.com \
--cc=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=mingo@elte.hu \
--cc=roland@redhat.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=viro@zeniv.linux.org.uk \
/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.