From: Willy Tarreau <wtarreau@hera.kernel.org>
To: linux-kernel@vger.kernel.org
Subject: Linux 2.4.37.2
Date: Sun, 7 Jun 2009 20:01:47 +0000 [thread overview]
Message-ID: <20090607200147.GA29197@hera.kernel.org> (raw)
I've just released Linux 2.4.37.2.
The main goal was to address a regression brought by 2.4.37.1. The
CAP_KILL fix caused modprobe to leave zombies on auto-loading (easily
seen with CONFIG_IPV6=m).
While working on this, I also merged some fixes which did not get into
2.4.37.1 either because it was too late or because I missed them. The
only really relevant one is the fix for the SCTP overflow (CVE-2009-0065)
which has been demonstrated to be remotely exploitable when an SCTP
application was running.
Users of 2.4.37.1 with modules autoloading enabled are really encouraged
to upgrade.
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.2.bz2
ftp://ftp.kernel.org/pub/linux/kernel/v2.4/ChangeLog-2.4.37.2
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
Regards,
Willy
Summary of changes from v2.4.37.1 to v2.4.37.2
============================================
David S. Miller (1):
ipv6: Disallow rediculious flowlabel option sizes.
Eugene Teo (1):
net: amend the fix for SO_BSDCOMPAT gsopt infoleak
Jesse Brandeburg (1):
e1000: fix bug with shared interrupt during reset
Neil Horman (1):
e1000: add missing length check to e1000 receive routine
Wei Yongjun (1):
sctp: Avoid memory overflow while FWD-TSN chunk is received with bad stream ID
Willy Tarreau (2):
exit_notify: fix regression uncovered by the CAP_KILL fix
Change VERSION to 2.4.37.2
reply other threads:[~2009-06-07 20:01 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=20090607200147.GA29197@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