From: Tomas Szepe <szepe@pinerecords.com>
To: Diego Calleja <grundig@teleline.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mremap bug and 2.4?
Date: Mon, 5 Jan 2004 19:23:54 +0100 [thread overview]
Message-ID: <20040105182354.GH1947@louise.pinerecords.com> (raw)
In-Reply-To: <20040105181053.6560e1e3.grundig@teleline.es>
On Jan-05 2004, Mon, 18:10 +0100
Diego Calleja <grundig@teleline.es> wrote:
> El Mon, 5 Jan 2004 13:26:23 -0200 (BRST) Marcelo Tosatti <marcelo.tosatti@cyclades.com> escribió:
>
> > On Mon, 5 Jan 2004, Robert L. Harris wrote:
> > > Just read this on full disclosure:
> > >
> > > http://isec.pl/vulnerabilities/isec-0013-mremap.txt
> [...]
> > It is possible that the problem is exploitable. There is no known public
> > exploit yet, however.
> >
> > 2.4.24 includes a fix for this (mm/mremap.c diff)
>
> It names 2.2 too. Is there a fix for 2.2?
Ask Alan. He's not following the kernel mailing list too closely these days.
--
Tomas Szepe <szepe@pinerecords.com>
next prev parent reply other threads:[~2004-01-05 18:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 14:54 mremap bug and 2.4? Robert L. Harris
2004-01-05 15:21 ` Erik Mouw
2004-01-05 15:26 ` Marcelo Tosatti
2004-01-05 15:42 ` Robert L. Harris
2004-01-05 17:10 ` Diego Calleja
2004-01-05 18:23 ` Tomas Szepe [this message]
2004-01-05 18:26 ` mremap() bug and 2.2? Petr Baudis
2004-01-05 22:55 ` mremap() bug IMHO not in 2.2 Petr Baudis
2004-01-05 23:36 ` Linus Torvalds
2004-01-05 23:58 ` Valdis.Kletnieks
2004-01-06 0:08 ` Linus Torvalds
2004-01-06 2:14 ` Tomas Szepe
2004-01-06 9:22 ` Martin Loschwitz
2004-01-06 20:36 ` mremap() bug indeed not in 2.2 (confirmed) Petr Baudis
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=20040105182354.GH1947@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=grundig@teleline.es \
--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