From: Ville Herva <vherva@viasys.com>
To: Chris Wright <chrisw@osdl.org>
Cc: Nur Hussein <obiwan@slackware.org.my>, linux-kernel@vger.kernel.org
Subject: mremap patches for 2.4 and 2.2?
Date: Fri, 20 Feb 2004 08:44:59 +0200 [thread overview]
Message-ID: <20040220064459.GF3767@viasys.com> (raw)
In-Reply-To: <20040219095636.D22989@build.pdx.osdl.net>
On Thu, Feb 19, 2004 at 09:56:36AM -0800, you [Chris Wright] wrote:
> * Nur Hussein (obiwan@slackware.org.my) wrote:
> > However, I am still intrigued by this fix:
> >
> > http://linux.bkbits.net:8080/linux-2.4/diffs/mm/mremap.c@1.7?nav=cset@1.1136.94.4
> >
> > It does not seem to be in 2.6.3. I can only assume 2.6.x does not
> > require it? The Changeset says it is to prevent a potential exploit by
> > the malicious use of mremap().
>
> It's fixed in 2.6 as well.
>
> http://linux.bkbits.net:8080/linux-2.5/diffs/mm/mremap.c@1.35?nav=index.html|src/|src/mm|hist/mm/mremap.c
Are these the sole patches one should apply for this vulnerability if
patching an older 2.4 or 2.6?
Is there a patch for 2.2 somewhere?
-- v --
v@iki.fi
next prev parent reply other threads:[~2004-02-20 6:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 14:37 Security update patch to 2.6.3 for mremap()? Nur Hussein
2004-02-19 16:00 ` Diego Calleja García
2004-02-19 17:37 ` Chris Wright
2004-02-19 17:43 ` Nur Hussein
2004-02-19 17:56 ` Chris Wright
2004-02-20 6:44 ` Ville Herva [this message]
[not found] <200402200946.i1K9k2OH015422@sunrise.pg.gda.pl>
2004-02-20 10:13 ` mremap patches for 2.4 and 2.2? Andrzej Krzysztofowicz
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=20040220064459.GF3767@viasys.com \
--to=vherva@viasys.com \
--cc=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=obiwan@slackware.org.my \
/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