public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Some questions about VM flags
Date: Wed, 23 Mar 2005 19:47:52 -0600	[thread overview]
Message-ID: <42421C48.6010600@shaw.ca> (raw)
In-Reply-To: <3LnM0-5Wf-27@gated-at.bofh.it>

Luca Falavigna wrote:
> Shouldn't printf generate a segfault trying to read a variabile located in a
> write-only area?

What architecture is this on? On many CPUs it is not possible to enforce 
a write-only memory area in most cases (there is no way to give write 
permissions without giving read permissions).

> 
> Shellcode lies in this segment. It is executed even if VM_EXEC isn't set. I
> think execution shouldn't be permitted if only VM_READ or VM_WRITE flags are
> set. Buffer overflows/format string based exploits wouldn't be so popular if we
> implemented this feaure. Please let me know your opinion.

Likewise, many CPUs cannot enforce execution restrictions separate from 
read restrictions (x86 CPUs are like this, except for the latest ones 
with NX support, or if you're using a kernel patch like exec-shield that 
tries to emulate this support).

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2005-03-24  1:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3LnM0-5Wf-27@gated-at.bofh.it>
2005-03-24  1:47 ` Robert Hancock [this message]
2005-03-23 16:01 Some questions about VM flags Luca Falavigna

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=42421C48.6010600@shaw.ca \
    --to=hancockr@shaw.ca \
    --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