From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755194AbcHSBWt (ORCPT ); Thu, 18 Aug 2016 21:22:49 -0400 Received: from mail-lf0-f46.google.com ([209.85.215.46]:34720 "EHLO mail-lf0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755236AbcHSBWC (ORCPT ); Thu, 18 Aug 2016 21:22:02 -0400 MIME-Version: 1.0 In-Reply-To: <800588f1-32d0-a4cc-821d-d31eef8921e7@redhat.com> References: <800588f1-32d0-a4cc-821d-d31eef8921e7@redhat.com> From: Dmitry Vyukov Date: Thu, 18 Aug 2016 17:16:56 -0700 Message-ID: Subject: Re: NULL-ptr deref in kvm_arch_vcpu_ioctl under AMD CPUs To: Paolo Bonzini Cc: =?UTF-8?B?Um9iZXJ0IMWad2nEmWNraQ==?= , LKML , Borislav Petkov Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.home.local id u7J1N0sO028672 On Thu, Aug 18, 2016 at 4:58 AM, Paolo Bonzini wrote: > > > On 19/02/2016 15:06, Robert Święcki wrote: >> Hi, >> >> This seems non-exploitable due to mmap_min_addr, so I guess it should >> be treated just as a regular bug > > Probably fixed by commit 4c5ea0a9cd02 ("locking/static_key: Fix > concurrent static_key_slow_inc()", 2016-06-21). There should be no > outstanding syzkaller reports for KVM now! Thanks for the update. I will try to reenable kvm fuzzing on my syzkaller instances. Just to make sure, you mean all bugs prefixed with kvm: here, right? https://github.com/google/syzkaller/wiki/Found-Bugs