All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <wtarreau@hera.kernel.org>
To: linux-kernel@vger.kernel.org
Subject: Linux 2.4.36.8
Date: Sun, 19 Oct 2008 21:31:07 +0000	[thread overview]
Message-ID: <20081019213107.GA20481@hera.kernel.org> (raw)


I've just released Linux 2.4.36.8.

It contains various fixes, 3 of which are for medium local security
issues. While not critical, it is suggested that 2.4.36 setups with
untrusted local users upgrade to 2.4.36.8.

The patch and changelog will appear soon at the following locations:
  ftp://ftp.all.kernel.org/pub/linux/kernel/v2.4/
  ftp://ftp.all.kernel.org/pub/linux/kernel/v2.4/patch-2.4.36.8.bz2
  ftp://ftp.all.kernel.org/pub/linux/kernel/v2.4/ChangeLog-2.4.36.8

Git repository:
   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.4.36.y.git
  http://www.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.4.36.y.git

Git repository through the gitweb interface:
  http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.4.36.y.git


Willy

---
Summary of changes from v2.4.36.7 to v2.4.36.8
============================================

Arjan van de Ven (1):
      security: avoid calling a NULL function pointer in drivers/video/tvaudio.c

Erik Inge Bolsø (1):
      doc: mention chain-compiling for really old gccs

Eugene Teo (2):
      CVE-2008-3275 Linux kernel local filesystem DoS
      Remove suid/sgid bits on truncate() (CVE-2008-4210)

Gilles Espinasse (1):
      tcp: Clear probes_out more aggressively in tcp_ack().

Willy Tarreau (4):
      x86 would not build without CONFIG_VT
      pc_keyb: fix breakage on ia64/mips/mips64
      doc: fix examples and add suggestions about depmod
      Change VERSION to 2.4.36.8

Yasuyuki KOZAKAI (1):
      netfilter: ip6t_{hbh,dst}: Rejects not-strict mode on rule insertion


                 reply	other threads:[~2008-10-19 21:31 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=20081019213107.GA20481@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.