From: Greg KH <greg@kroah.com>
To: "Charles (Chas) Williams" <3chas3@gmail.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 3.14] udf: Check length of extended attributes and allocation descriptors
Date: Tue, 29 Sep 2015 16:13:21 +0200 [thread overview]
Message-ID: <20150929141321.GE24418@kroah.com> (raw)
In-Reply-To: <1441313329.2546.38.camel@gmail.com>
On Thu, Sep 03, 2015 at 04:48:49PM -0400, Charles (Chas) Williams wrote:
> From: Jan Kara <jack@suse.cz>
>
> commit 23b133bdc452aa441fcb9b82cbf6dd05cfd342d0 upstream.
>
> 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.
>
> This fixes CVE-2015-4167.
>
> Reported-by: Carl Henrik Lunde <chlunde@ping.uio.no>
> Signed-off-by: Jan Kara <jack@suse.cz>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> [Use make_bad_inode() instead of branching due to older implementation.]
> Signed-off-by: Chas Williams <3chas3@gmail.com>
Thanks for this, now applied.
greg k-h
prev parent reply other threads:[~2015-09-29 14:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 20:48 [PATCH 3.14] udf: Check length of extended attributes and allocation descriptors Charles (Chas) Williams
2015-09-29 14:13 ` 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=20150929141321.GE24418@kroah.com \
--to=greg@kroah.com \
--cc=3chas3@gmail.com \
--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 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.