Received: by 2002:a05:6a10:a852:0:0:0:0 with SMTP id d18csp1272560pxy; Thu, 6 May 2021 04:38:53 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxICRTE8aXfAdVCoYnTZ1aFGdeqjS95Zvt1FjQIhQQplzHKcNQJ7/p8Ng3EmFFeC3BqiKVr X-Received: by 2002:a17:906:ccc9:: with SMTP id ot9mr3823888ejb.253.1620301133335; Thu, 06 May 2021 04:38:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1620301133; cv=none; d=google.com; s=arc-20160816; b=gq/Rl9vEzdHcT+YQOSAznFrJY+ziz619Q36P/CHZUMMnC1PCeF7q3erutjNmKGf+2I bf+oVsdUOBORYG69DOmhCPYuBgkPT9wL/QxCCKjaM4IAmZBV0MDPNpCK8TYhqI3vJK4Q zY5V6tuoF4GcXS4TddI6oB6qWdd7Ojz0w8pITF0jFxKompcl2O1gkCYSUwtS18xfKdgG T2NSSRefaAe4OVS2mv1dVFxjeVW9YMPUmfuUR3cL5SuWQc7HD07jq7HHdTMe5WnQ+/34 bgVsaYomuPvgYfxuU/enK/4SDoPRxiJGjMdey3lFhvbfVnV9jisadJnQ5d/6fJYd05PP PHUg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature; bh=IcruxJx/IBHZiLRdPQHrzdMkqW/EMFC2L1rirQLSBsk=; b=HPuhvVV8Ds3bGQXh7MWGwZ8UkHO/kDHcrz9moOwUo7/bHTr+WpN8APQik0W0tuQEpV uJHsI08ir1IialTxU+XtGqobQqSoq9mc/xF8e3FwFkiZpgVW7x+avJz1/qz/cpzgvtf5 XMnUt07pO93eAnoswCn2m4oML+18LIAl+C5zd1jiOOVDaLDyn4OcSPAJLwDf8oIoayMm uciSZ0kVyH6kqrLbYA5nvLflkv0wu31MP4qz3J+pPsdbC6sFcNg66yHb7E7ud5Kk9JTB Mk4EC89ghfsn+nmzQlpW2IS36V/nk3nxPeawdEgmSl4WEgGzIdtcDGPlfJouWo2HBUja TOtA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=TDYvu7c2; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id m10si1587438eji.560.2021.05.06.04.38.29; Thu, 06 May 2021 04:38:53 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=TDYvu7c2; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234833AbhEFLgF (ORCPT + 99 others); Thu, 6 May 2021 07:36:05 -0400 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:47404 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234603AbhEFLgE (ORCPT ); Thu, 6 May 2021 07:36:04 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1620300906; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=IcruxJx/IBHZiLRdPQHrzdMkqW/EMFC2L1rirQLSBsk=; b=TDYvu7c2J+T/LHKIFLqFTqDOC8rfcFQSlkNL5muVAuEQxzhiLtzgbo1holebac9A/fyZJ3 G0G6FGv/gLA9/MB89qsfr6HjaoMgoOxi3BzDOBffYgFOewKQK2CtR3cgFtEmJFgkpjldph QDFmw7xq4u8HidoNEPTFaIIgTKp131Q= Received: from mail-ej1-f69.google.com (mail-ej1-f69.google.com [209.85.218.69]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-497-TIicNdJgPMazkuDiAQzpDw-1; Thu, 06 May 2021 07:35:05 -0400 X-MC-Unique: TIicNdJgPMazkuDiAQzpDw-1 Received: by mail-ej1-f69.google.com with SMTP id gt39-20020a1709072da7b02903a8f7736a08so467270ejc.1 for ; Thu, 06 May 2021 04:35:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=IcruxJx/IBHZiLRdPQHrzdMkqW/EMFC2L1rirQLSBsk=; b=tlH6rypkFliCDBkdojLfqJ1oOZpNV8AQmACMmRZ21YzRHgiRi4evrNeVERGYZKwJfX rhDuRMKKxIOkhh2tRspXxHQj+HfbsM2LhtNrznYmyXkV3zQvLQJtNYNxFca+3lGgSFVB PcAaMpEDy+Kk2kZwVdiHZYHNm8/zz1gFDCrk0BXwJOmnqnhRh8oJ7SlcMg9eP/ZbGls9 Qh6QLk8mssuFE3uoiULoKwStniEk6GBCIg4dgLok/r8a5UTSKqDCkH+Ou6zNx4Nt/J02 npS9O8o2B4fWOXhj7kIQYkYmheblFOWI2fWalynZPnyAsv0sZnxQ2JDnAoRYhSaMszQG IKIg== X-Gm-Message-State: AOAM531pWRejB7Q1nTOg2dN4VDtQlp2vHbGpIvm2x4SZVloIFvFo50sL SLLX1zoQFWtG676XN90XD0FDMjdqMH1jpwbIMpRRH9pJjweh4Ye09Omi95HDgxSJA4NnUmPumG/ lqnkpYd/3RLkBjmZH4y9gDkZN0rgzWGP1cRq6URGHz9SAh3rLCj7wMSkcGzTRO3c/qI38X+T4pi tH X-Received: by 2002:a17:906:dffb:: with SMTP id lc27mr2495225ejc.469.1620300903699; Thu, 06 May 2021 04:35:03 -0700 (PDT) X-Received: by 2002:a17:906:dffb:: with SMTP id lc27mr2495192ejc.469.1620300903297; Thu, 06 May 2021 04:35:03 -0700 (PDT) Received: from ?IPv6:2001:b07:6468:f312:c8dd:75d4:99ab:290a? ([2001:b07:6468:f312:c8dd:75d4:99ab:290a]) by smtp.gmail.com with ESMTPSA id i6sm1447225eds.83.2021.05.06.04.35.02 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 06 May 2021 04:35:02 -0700 (PDT) Subject: Re: KVM: x86: Cancel pvclock_gtod_work on module removal To: Thomas Gleixner , kvm@vger.kernel.org Cc: Sean Christopherson , x86@kernel.org, LKML References: <87czu4onry.ffs@nanos.tec.linutronix.de> From: Paolo Bonzini Message-ID: <2a18634f-b100-334e-f7b5-01c84302e27e@redhat.com> Date: Thu, 6 May 2021 13:35:01 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 MIME-Version: 1.0 In-Reply-To: <87czu4onry.ffs@nanos.tec.linutronix.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05/05/21 23:48, Thomas Gleixner wrote: > Nothing prevents the following: > > pvclock_gtod_notify() > queue_work(system_long_wq, &pvclock_gtod_work); > ... > remove_module(kvm); > ... > work_queue_run() > pvclock_gtod_work() <- UAF > > Ditto for any other operation on that workqueue list head which touches > pvclock_gtod_work after module removal. > > Cancel the work in kvm_arch_exit() to prevent that. > > Fixes: 16e8d74d2da9 ("KVM: x86: notifier for clocksource changes") > Signed-off-by: Thomas Gleixner > --- > Found by inspection because of: > https://lkml.kernel.org/r/0000000000001d43ac05c0f5c6a0@google.com > See also: > https://lkml.kernel.org/r/20210505105940.190490250@infradead.org > > TL;DR: Scheduling work with tk_core.seq write held is a bad idea. > --- > arch/x86/kvm/x86.c | 1 + > 1 file changed, 1 insertion(+) > > --- a/arch/x86/kvm/x86.c > +++ b/arch/x86/kvm/x86.c > @@ -8168,6 +8168,7 @@ void kvm_arch_exit(void) > cpuhp_remove_state_nocalls(CPUHP_AP_X86_KVM_CLK_ONLINE); > #ifdef CONFIG_X86_64 > pvclock_gtod_unregister_notifier(&pvclock_gtod_notifier); > + cancel_work_sync(&pvclock_gtod_work); > #endif > kvm_x86_ops.hardware_enable = NULL; > kvm_mmu_module_exit(); > Queued, thanks (with added Cc to stable). Paolo