public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Robert L. Harris" <Robert.L.Harris@rdlg.net>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: mremap bug and 2.4?
Date: Mon, 5 Jan 2004 10:42:31 -0500	[thread overview]
Message-ID: <20040105154231.GD2247@rdlg.net> (raw)
In-Reply-To: <Pine.LNX.4.58L.0401051323520.1188@logos.cnet>

[-- Attachment #1: Type: text/plain, Size: 1398 bytes --]



I love you guys.  Yeah, I have to compile a new kernel, test it  and push it out
this week to 600 machines but atleast I don't have to wait 6 months and
then hope it doesn't kill all my apps.

You guys are great, THANKS!

Robert


Thus spake Marcelo Tosatti (marcelo.tosatti@cyclades.com):

> 
> 
> On Mon, 5 Jan 2004, Robert L. Harris wrote:
> 
> >
> >
> > Just read this on full disclosure:
> >
> > http://isec.pl/vulnerabilities/isec-0013-mremap.txt
> >
> > Is it valid?  No working proof of concept code has been posted so I can't
> > test my systems.  The article only lists 2.4 and 2.6.  Is this
> > 2.4.16-current, etc?  Anyone have any details about versions that are
> > safe so I/We can determine if I need to roll a new production kernel out
> > again?
> 
> 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)

:wq!
---------------------------------------------------------------------------
Robert L. Harris                     | GPG Key ID: E344DA3B
                                         @ x-hkp://pgp.mit.edu
DISCLAIMER:
      These are MY OPINIONS ALONE.  I speak for no-one else.

Life is not a destination, it's a journey.
  Microsoft produces 15 car pileups on the highway.
    Don't stop traffic to stand and gawk at the tragedy.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-01-05 15:43 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 [this message]
2004-01-05 17:10   ` Diego Calleja
2004-01-05 18:23     ` Tomas Szepe
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=20040105154231.GD2247@rdlg.net \
    --to=robert.l.harris@rdlg.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox