From: GCS <gcs@lsc.hu>
To: Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.1-rc1 affected?
Date: Mon, 5 Jan 2004 20:38:17 +0100 [thread overview]
Message-ID: <20040105193817.GA4366@lsc.hu> (raw)
In-Reply-To: <Pine.LNX.4.58.0401051027430.2115@home.osdl.org>
On Mon, Jan 05, 2004 at 10:31:02AM -0800, Linus Torvalds <torvalds@osdl.org> wrote:
[snip]
> And because nobody has an exploit yet, and one may be hard or
> impossible to create?
There _is_ an exploit: http://isec.pl/vulnerabilities/isec-0013-mremap.txt
"Since no special privileges are required to use the mremap(2) system
call any process may misuse its unexpected behavior to disrupt the kernel
memory management subsystem. Proper exploitation of this vulnerability may
lead to local privilege escalation including execution of arbitrary code
with kernel level access. Proof-of-concept exploit code has been created
and successfully tested giving UID 0 shell on vulnerable systems."
Cheers,
GCS
next prev parent reply other threads:[~2004-01-05 19:53 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 [this message]
2004-01-05 22:48 ` Tomas Szepe
2004-01-06 0:23 ` Bastiaan Spandaw
2004-01-06 1:09 ` Max Valdez
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=20040105193817.GA4366@lsc.hu \
--to=gcs@lsc.hu \
--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 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.