From: Max Valdez <maxvalde@fis.unam.mx>
To: Bastiaan Spandaw <lkml@becobaf.com>
Cc: Tomas Szepe <szepe@pinerecords.com>,
kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.1-rc1 affected?
Date: Mon, 05 Jan 2004 19:09:37 -0600 [thread overview]
Message-ID: <1073351377.2690.1.camel@garaged.homeip.net> (raw)
In-Reply-To: <1073348624.1790.43.camel@louise3.void.org>
[-- Attachment #1: Type: text/plain, Size: 1347 bytes --]
At least it hangs a redhat 7.2 kernel
I will test it further tomorrow, but it looks like a good proof to me
Best regards
Max
On Mon, 2004-01-05 at 18:23, Bastiaan Spandaw wrote:
> On Mon, 2004-01-05 at 23:48, Tomas Szepe wrote:
> > On Jan-05 2004, Mon, 20:38 +0100
> > GCS <gcs@lsc.hu> wrote:
> >
> > > There _is_ an exploit: http://isec.pl/vulnerabilities/isec-0013-mremap.txt
> > > "Since no special privileges are required to use the mremap(2) system
> > ...
> >
> > I will not believe the claim until I've seen the code.
>
> Not sure if this works or not.
> According to a slashdot comment this is proof of concept code.
>
> http://linuxfromscratch.org/~devine/mremap_poc.c
>
> Regards,
>
> Bastiaan
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Linux garaged 2.4.24 #2 SMP Mon Jan 5 17:41:16 CST 2004 i686 Pentium III (Coppermine) GenuineIntel GNU/Linux
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GS/ d-s:a-28C++ILHA+++P+L++>+++E---W++N*o--K-w++++O-M--V--PS+PEY--PGP++t5XRtv++b++DI--D-G++e++h-r+y**
------END GEEK CODE BLOCK------
gpg-key: http://garaged.homeip.net/gpg-key.txt
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-06 1:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 16:31 2.6.1-rc1 affected? Markus Hästbacka
2004-01-05 16:41 ` [patchlet link] " Maciej Soltysiak
2004-01-05 16:46 ` Linus Torvalds
2004-01-05 18:14 ` Markus Hästbacka
2004-01-05 18:31 ` Linus Torvalds
2004-01-05 19:04 ` Markus Hästbacka
2004-01-05 19:38 ` GCS
2004-01-05 22:48 ` Tomas Szepe
2004-01-06 0:23 ` Bastiaan Spandaw
2004-01-06 1:09 ` Max Valdez [this message]
2004-01-06 1:25 ` Jesper Juhl
2004-01-06 1:31 ` Hugang
2004-01-06 1:43 ` Hugang
2004-01-06 2:47 ` szonyi calin
2004-01-06 3:24 ` Jonathan Higdon
2004-01-06 3:51 ` szonyi calin
2004-01-06 6:39 ` Jakob Oestergaard
2004-01-06 9:26 ` Giuliani Ivan
[not found] <1aFW7-39l-11@gated-at.bofh.it>
[not found] ` <1aG5G-3mf-21@gated-at.bofh.it>
2004-01-06 12:44 ` Michal Schmidt
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=1073351377.2690.1.camel@garaged.homeip.net \
--to=maxvalde@fis.unam.mx \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@becobaf.com \
--cc=szepe@pinerecords.com \
/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.