From: Greg KH <gregkh@linuxfoundation.org>
To: "Thomas D." <whissi@whissi.de>
Cc: stable@vger.kernel.org
Subject: Re: Request for stable 3.{4,10,14} inclusion: Fix for CVE-2015-4167
Date: Tue, 29 Sep 2015 15:37:23 +0200 [thread overview]
Message-ID: <20150929133723.GA24418@kroah.com> (raw)
In-Reply-To: <55D1B19A.4060100@whissi.de>
On Mon, Aug 17, 2015 at 12:04:10PM +0200, Thomas D. wrote:
> Hi,
>
> seems like the following stable kernels are still missing the following
> fix for CVE-2015-4167:
>
> - 3.14
> - 3.10
> - 3.4
>
> > Commit: 23b133bdc452aa441fcb9b82cbf6dd05cfd342d0
> > From: Jan Kara
> > Date: Wed, 7 Jan 2015 13:49:08 +0100
> > Subject: udf: Check length of extended attributes and allocation
> > descriptors
> >
> > Check length of extended attributes and allocation descriptors when
> > loading inodes from disk. Otherwise corrupted filesystems could confuse
> > the code and make the kernel oops.
It doesn't apply to the 3.14 or 3.10-stable kernels, care to provide a
tested backport?
thanks,
greg k-h
prev parent reply other threads:[~2015-09-29 13:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 10:04 Request for stable 3.{4,10,14} inclusion: Fix for CVE-2015-4167 Thomas D.
2015-09-29 13:37 ` Greg KH [this message]
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=20150929133723.GA24418@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=whissi@whissi.de \
/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).