From: Nur Hussein <obiwan@slackware.org.my>
To: linux-kernel@vger.kernel.org
Subject: Re: Security update patch to 2.6.3 for mremap()?
Date: Fri, 20 Feb 2004 01:43:02 +0800 [thread overview]
Message-ID: <1077212582.223.17.camel@sophia.localdomain> (raw)
In-Reply-To: <20040219170051.6b97f6bf.diegocg@teleline.es>
Thank you for the clarification, and I apologize for my previous email
which went horribly wrong wrt formatting.
> AFAIK, the 2.4 path should be this one, shouldn't it?
> http://linux.bkbits.net:8080/linux-2.4/patch@1.1323?nav=index.html|ChangeSet@-2d|cset@1.1323
> http://linux.bkbits.net:8080/linux-2.5/diffs/mm/mremap.c@1.38?nav=index.html|src/|src/mm|hist/mm/mremap.c
> 2.6.3 is safe, it seems
Yes, those two patches seem to match up.
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().
-= Nur Hussein =-
next prev parent reply other threads:[~2004-02-19 17:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 14:37 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 [this message]
2004-02-19 17:56 ` Chris Wright
2004-02-20 6:44 ` mremap patches for 2.4 and 2.2? Ville Herva
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=1077212582.223.17.camel@sophia.localdomain \
--to=obiwan@slackware.org.my \
--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
all inboxes | Powered by JetHome®