From: Willy Tarreau <wtarreau@hera.kernel.org>
To: linux-kernel@vger.kernel.org
Subject: Linux 2.4.37.5
Date: Thu, 13 Aug 2009 22:26:15 +0000 [thread overview]
Message-ID: <20090813222615.GA5675@hera.kernel.org> (raw)
Hi all,
I've just released Linux 2.4.37.5.
I wanted to delay it a bit more to wait for other fixes to be ready
to be merged, but a very old vulnerability has recently been discovered,
and a local exploit is already circulating, though it does not work as-is
on 2.4, hehe ;-)
Thus I preferred to release 2.4.37.5 now so that users have the time
to patch before someone figures how to modify the exploit to get it
to work on 2.4. The issue only affects systems with untrusted local
users. For those who don't have time to revalidate and upgrade, just
set /proc/sys/vm/mmap_min_addr to 4096 or more, as it is enough to
stop the exploit, and is recommended anyway, unless you know that it
breaks one very old legacy application.
A few minor build issues have also been fixed BTW.
The patch and changelog will appear soon at the following locations:
ftp://ftp.kernel.org/pub/linux/kernel/v2.4/
ftp://ftp.kernel.org/pub/linux/kernel/v2.4/patch-2.4.37.5.bz2
ftp://ftp.kernel.org/pub/linux/kernel/v2.4/ChangeLog-2.4.37.5
Git repository:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.4.37.y.git
http://www.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.4.37.y.git
Git repository through the gitweb interface:
http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.4.37.y.git
Willy
--
Summary of changes from v2.4.37.4 to v2.4.37.5
============================================
Willy Tarreau (5):
build: fix for "make rpm" on RH9
build: fix genksyms segfault in pcigame.c
build: do not let genksyms silently fail anymore
net: fix possible NULL dereference in sock_sendpage()
Change VERSION to 2.4.37.5
reply other threads:[~2009-08-13 22:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090813222615.GA5675@hera.kernel.org \
--to=wtarreau@hera.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=w@1wt.eu \
/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