stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: stable <stable@vger.kernel.org>
Subject: Re: Security fixes for 2.6.32-stable
Date: Mon, 16 Nov 2015 21:08:22 +0100	[thread overview]
Message-ID: <20151116200822.GA30245@1wt.eu> (raw)
In-Reply-To: <1447703257.17039.138.camel@decadent.org.uk>

Hi Ben,

On Mon, Nov 16, 2015 at 07:47:37PM +0000, Ben Hutchings wrote:
> Willy, here are the security patches I've recently applied to Debian's
> 2.6.32 branch, aside from those for CVE-2015-2925 - which we already
> discussed - and for issues not yet fixed upstream.
> 
> These have already been released without reported regressions. The
> mapping to CVE IDs is:
> 
> � * md: use kzalloc() when bitmap is disabled�(CVE-2015-5697)
> � * ipv6: addrconf: validate new MTU before applying it�(CVE-2015-0272)
> � * virtio-net: drop NETIF_F_FRAGLIST�(CVE-2015-5156)
> � * USB: whiteheat: fix potential null-deref at probe�(CVE-2015-5257)
> � * ipc/sem.c: fully initialize sem_array before making it visible
>     (no CVE ID, but similar issue to the following fix)
> � * Initialize msg/shm IPC objects before doing ipc_addid()
>     (CVE-2015-7613)

Much appreciated, thank you! I'll try to issue a new kernel ASAP, probably
next week.

Cheers,
Willy


  reply	other threads:[~2015-11-16 20:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-16 19:47 Security fixes for 2.6.32-stable Ben Hutchings
2015-11-16 20:08 ` Willy Tarreau [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-02-05 17:45 Ben Hutchings
2016-02-05 18:11 ` Willy Tarreau
2016-01-17 14:30 Ben Hutchings
2016-01-17 17:28 ` Willy Tarreau
2015-12-27 20:45 Ben Hutchings
2015-12-27 20:50 ` Willy Tarreau
2015-07-05 21:19 Ben Hutchings

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=20151116200822.GA30245@1wt.eu \
    --to=w@1wt.eu \
    --cc=ben@decadent.org.uk \
    --cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).