From: David Hinds <dhinds@sonic.net>
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, Junfeng Yang <yjf@stanford.edu>
Subject: Re: [CHECKER] pcmcia user-pointer dereference
Date: Thu, 29 May 2003 14:36:24 -0700 [thread overview]
Message-ID: <20030529143624.A10639@sonic.net> (raw)
In-Reply-To: <D43209EB-921C-11D7-B8B8-000A95A0560C@us.ibm.com>
On Thu, May 29, 2003 at 04:30:54PM -0500, Hollis Blanchard wrote:
>
> That's true for pcmcia_get_mem_page. However pcmcia_map_mem_page writes
> into the structure it verifies. I think pcmcia_get_first/next_window
> could also be used to corrupt memory (*handle = win in
> pcmcia_get_window).
The map_mem_page ioctl can only be used by root. The get_*_window
ioctl's can't corrupt anything because they, like get_mem_page, only
read the target data structures.
-- Dave
next prev parent reply other threads:[~2003-05-29 21:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-29 21:11 [CHECKER] pcmcia user-pointer dereference Hollis Blanchard
2003-05-29 21:22 ` David Hinds
2003-05-29 21:30 ` Hollis Blanchard
2003-05-29 21:36 ` David Hinds [this message]
2003-05-30 10:11 ` Alan Cox
2003-05-30 10:10 ` Alan Cox
2003-05-31 22:46 ` David Wagner
[not found] <E19LjBL-0000FS-00@mrrp.telinco.co.uk>
2003-05-30 12:43 ` Mike Playle
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=20030529143624.A10639@sonic.net \
--to=dhinds@sonic.net \
--cc=hollisb@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yjf@stanford.edu \
/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