From: Greg KH <gregkh@linuxfoundation.org>
To: Wang Kai <morgan.wang@huawei.com>
Cc: stable@vger.kernel.org, pbonzini@redhat.com
Subject: Re: [PATCH] kvm: x86: fix kvm_apic_has_events to check for NULL pointer
Date: Fri, 14 Aug 2015 09:58:05 -0700 [thread overview]
Message-ID: <20150814165805.GC32313@kroah.com> (raw)
In-Reply-To: <1438145794-187789-2-git-send-email-morgan.wang@huawei.com>
On Wed, Jul 29, 2015 at 04:56:34AM +0000, Wang Kai wrote:
> From: Paolo Bonzini <pbonzini@redhat.com>
>
> commit ce40cd3fc7fa40a6119e5fe6c0f2bc0eb4541009 upstream.
>
> Malicious (or egregiously buggy) userspace can trigger it, but it
> should never happen in normal operation.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> [wangkai: backport to 3.10: adjust context]
It needs to go to all stable trees, not just 3.10, so I've applied it to
the ones I manage.
thanks,
greg k-h
prev parent reply other threads:[~2015-08-14 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 4:56 [PATCH][request for stable 3.10 inclusion]CVE-2015-4692 Wang Kai
2015-07-29 4:56 ` [PATCH] kvm: x86: fix kvm_apic_has_events to check for NULL pointer Wang Kai
2015-07-29 8:19 ` Paolo Bonzini
2015-08-14 16:58 ` 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=20150814165805.GC32313@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=morgan.wang@huawei.com \
--cc=pbonzini@redhat.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 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).