public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@suse.de>
To: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	torvalds@linux-foundation.org, stable@kernel.org
Subject: Linux 2.6.23.8
Date: Fri, 16 Nov 2007 10:37:52 -0800	[thread overview]
Message-ID: <20071116183752.GA9807@kroah.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 1537 bytes --]

We (the -stable team) are announcing the release of the 2.6.23.8 kernel.
It contains a few serious security fixes, as well as a raft of other
bugfixes and stuff from the last 2.6.23.1 kernel release.

Wait, what happened to versions 2.6.23.2 - 7 you might ask?  Well, they
too are released, and I'll be responding to this message with those
individual changelogs and diffs.  They corrispond to the different patch
groups that I sent out for review of the stable tree in order to handle
the huge number of overall patches.  This way, if problems occur, it
will be easier for people to track down where the regression might have
happened.

I'll also be replying to this message with a copy of the patch between
2.6.23.7 and 2.6.23.8

The updated 2.6.23.y git tree can be found at:
        git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.23.y.git
and can be browsed at the normal kernel.org git web browser:
        http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.23.y.git;a=summary

thanks,

greg k-h

--------

 Makefile             |    2 +-
 kernel/exit.c        |    3 +--
 net/ipv4/tcp_input.c |    5 +++++
 3 files changed, 7 insertions(+), 3 deletions(-)

Summary of changes from v2.6.23.7 to v2.6.23.8
==============================================

Greg Kroah-Hartman (1):
      Linux 2.6.23.8

Ilpo Järvinen (1):
      TCP: Make sure write_queue_from does not begin with NULL ptr (CVE-2007-5501)

Roland McGrath (1):
      wait_task_stopped: Check p->exit_state instead of TASK_TRACED (CVE-2007-5500)


             reply	other threads:[~2007-11-16 18:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-16 18:37 Greg Kroah-Hartman [this message]
2007-11-16 18:38 ` Linux 2.6.23.8 Greg Kroah-Hartman
2007-11-16 18:39 ` Linux 2.6.23.2 Greg Kroah-Hartman
2007-11-16 18:39   ` Greg Kroah-Hartman
2007-11-16 19:35   ` Mark Lord
2007-11-16 19:39     ` Matti Aarnio
2007-11-16 19:57       ` Matt Mackall
2007-11-16 23:35         ` David Woodhouse
2007-11-18  1:38         ` Krzysztof Halasa
2007-11-16 20:10       ` Greg KH
2007-11-16 18:44 ` Linux 2.6.23.3 Greg Kroah-Hartman
2007-11-16 18:44   ` Greg Kroah-Hartman
2007-11-16 23:15   ` Michael Tokarev
2007-11-17  1:03     ` Greg KH
2007-11-16 18:46 ` Linux 2.6.23.4 Greg Kroah-Hartman
2007-11-16 18:46   ` Greg Kroah-Hartman
2007-11-16 18:47 ` Linux 2.6.23.5 Greg Kroah-Hartman
2007-11-16 18:47   ` Greg Kroah-Hartman
2007-11-16 18:48 ` Linux 2.6.23.6 Greg Kroah-Hartman
2007-11-16 18:49   ` Greg Kroah-Hartman
2007-11-16 18:50 ` Linux 2.6.23.7 Greg Kroah-Hartman
2007-11-16 18:50   ` Greg Kroah-Hartman

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=20071116183752.GA9807@kroah.com \
    --to=gregkh@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    --cc=torvalds@linux-foundation.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