From: Greg KH <gregkh@suse.de>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@osdl.org>, torvalds@osdl.org, stable@kernel.org
Subject: Linux 2.6.17.10
Date: Tue, 22 Aug 2006 12:27:28 -0700 [thread overview]
Message-ID: <20060822192727.GA8579@kroah.com> (raw)
We (the -stable team) are announcing the release of the 2.6.17.10 kernel.
It contains three security fixes: one for SCTP, one for UDF filesystems,
and one that only can be triggered by a local root user.
I'll also be replying to this message with a copy of the patch between
2.6.17.9 and 2.6.17.10, as it is small enough to do so.
The updated 2.6.17.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.17.y.git
and can be browsed at the normal kernel.org git web browser:
www.kernel.org/git/
thanks,
greg k-h
--------
Makefile | 2 -
block/elevator.c | 3 +-
fs/udf/super.c | 2 -
fs/udf/truncate.c | 64 ++++++++++++++++++++++++++++-------------------
include/net/sctp/sctp.h | 13 ---------
include/net/sctp/sm.h | 3 --
net/sctp/sm_make_chunk.c | 30 ++++++----------------
net/sctp/sm_statefuns.c | 20 ++------------
net/sctp/socket.c | 10 ++++++-
9 files changed, 66 insertions(+), 81 deletions(-)
Summary of changes from v2.6.17.9 to v2.6.17.10
===============================================
Greg Kroah-Hartman:
Linux 2.6.17.10
Jan Kara:
Fix possible UDF deadlock and memory corruption (CVE-2006-4145)
Oleg Nesterov:
elv_unregister: fix possible crash on module unload
Sridhar Samudrala:
Fix sctp privilege elevation (CVE-2006-3745)
next reply other threads:[~2006-08-22 19:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 19:27 Greg KH [this message]
2006-08-22 19:28 ` Greg KH
2006-08-23 8:35 ` Matthias Andree
2006-08-23 8:41 ` Greg KH
2006-08-23 8:54 ` Jan Engelhardt
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=20060822192727.GA8579@kroah.com \
--to=gregkh@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=torvalds@osdl.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®