Received: by 2002:a05:6359:c8b:b0:c7:702f:21d4 with SMTP id go11csp4541001rwb; Tue, 20 Sep 2022 15:55:13 -0700 (PDT) X-Google-Smtp-Source: AMsMyM7YQycpSFUB6cgyGzKQcclWnmln4o18Otda1dbs5/hNdL53DEC/Yhlq13vP7cZU9zHzkfwi X-Received: by 2002:a17:903:11c5:b0:178:af17:e930 with SMTP id q5-20020a17090311c500b00178af17e930mr1802543plh.95.1663714512998; Tue, 20 Sep 2022 15:55:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1663714512; cv=none; d=google.com; s=arc-20160816; b=uhlo0SmW7Ee3S0jkT0uZndgfuEiN9XF/uE4PTGiqyXGsPKy6f0+S+bCSF7jNz2q+jq AUGUeI5eW1Ow2G6z1NzaE7SxgEpqYDfdz44Lz1aiQBrcnB43XYmNjM55MApongcO+5zE Eix/uGnqCQtuom6Wc1zEsgbJoaC+pOMaXQ3UWnk/9Gs5sdO8+UZPq0sM5O8WH64+hjyq 3FcE6KeJASCv7xPMKEY+Bpi7tDGtFex3xaH9/sYYlOz9Nbibl8GNJzUlSXBArnNB+pXx Cnskn/bgco0NypRXQNPzqeVL9fB6A4Xq8OQuwW+2Jg3bMIPF5M6SYBmCuArNgIL91TbN 2GJQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=Tg/AVsJjM4BQaOAFmZtyZph+a2NDWNsSd26JaLIUV6s=; b=h08lkjDM0YNU36jIoD70VhvaC7yzPDpU8tOiy4eD0iBUIZWyi8spYa9f6bZR8Ctvvd 9PFZJj8d2iu/QYzC3ReZFB6ZSphbMq9LQ+bh2m9WAbkq3kgrZtDoQ3scoZ2adXWGhulH D729umjF4p7VouKvu8wzsjaK98u6Bby5QY7EsK2Afgrv0C4H3cZnttzchZo6hw6k+7Mk NiFdcJatLljY9k8sEyUNK2GUOPjMHPlZGXeMWV/OQm0Al4jY5mZFDYdYJdmqOYg3FPHU eWAOsHnxOQNRZJgXNtaAFqS5dxnhX2NHw0QhYAPsj6PO3HiL0L5i1Rq8pwx/IdnWJjMA Q/jQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=e+4xFQ9V; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id m5-20020a170902f64500b001730984c2e7si835364plg.306.2022.09.20.15.55.01; Tue, 20 Sep 2022 15:55:12 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=e+4xFQ9V; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229917AbiITWpY (ORCPT + 99 others); Tue, 20 Sep 2022 18:45:24 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58048 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229512AbiITWpW (ORCPT ); Tue, 20 Sep 2022 18:45:22 -0400 Received: from mail-pl1-x62a.google.com (mail-pl1-x62a.google.com [IPv6:2607:f8b0:4864:20::62a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5E0334B0D1; Tue, 20 Sep 2022 15:45:21 -0700 (PDT) Received: by mail-pl1-x62a.google.com with SMTP id w10so2981571pll.11; Tue, 20 Sep 2022 15:45:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date; bh=Tg/AVsJjM4BQaOAFmZtyZph+a2NDWNsSd26JaLIUV6s=; b=e+4xFQ9VtKkeKiUV5Fi9LQ9G/FHPIrfhsYjxaPDm+oIF/Xqfgz9O+4MbKtLPACrM9Y OxCaEOr6niAug6lequ5LrYPKGmQamg/Aus2zwQZi5OTovUuFx6dh0bAlBPhdCQcb/ZEL MnlkhVMIwUomhL3+hzrn/HztgT3u4E0C2GDZu6tYTaIztFh4QdSFuHuViFe0aUjVxMLQ hJEG7oY2ODslxL4BgqEU3hKyS9kUwluN8eNmPx9lSg08Ql1A5hItuXw9mLLDg93wNoDM /qSx744zd13nUtEvbLXHjW880Ql7XItu/s8vhECuVMBLv0RHqvT+Nln7wDR/3Sam7hhC ikLg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date; bh=Tg/AVsJjM4BQaOAFmZtyZph+a2NDWNsSd26JaLIUV6s=; b=Dz3lgQ9cyZw286evrLtC+86H5FL0F9bJOKMPl5PwusUR4gsfrFn1JDC/irCGDnyYxO NATFklT9TCfgQ2PXSVwsIewvk8pcs5KCB8uIxt6BHAIYHf/nn04CTq6jS1J/NiqOBiNE OUOvzSmM7joT+S1dq2m05THHA64xfMYqtaol3j2RFUVNJ/lS4kpPaI3DUWvxCESp9BAq UojFbprbdS1gaFA4CPbwgRhZTiL8sGGZNBMkUWm41LDic3AUXngVdBy00C0ll5/6UfmV zD8Jv9Nb9Q4YncOXe6VdnZOfbuwJEkKVttCSYHSOtP2lqWxZoM4uWkn9M/PtPDJYmXcz hv3Q== X-Gm-Message-State: ACrzQf3WA3zpB7rb3rQG+yDrZedglcvS+K/5aNhrQi9NP9zl0cO4VUuC bNMlGo4XV+bQU9i+El6FtWY= X-Received: by 2002:a17:902:f7d2:b0:176:ca6b:eadb with SMTP id h18-20020a170902f7d200b00176ca6beadbmr1775618plw.173.1663713920646; Tue, 20 Sep 2022 15:45:20 -0700 (PDT) Received: from sc2-hs2-b1628.eng.vmware.com ([66.170.99.1]) by smtp.gmail.com with ESMTPSA id w3-20020aa79543000000b0052e6c058bccsm449613pfq.61.2022.09.20.15.45.19 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 20 Sep 2022 15:45:20 -0700 (PDT) From: Nadav Amit X-Google-Original-From: Nadav Amit To: Thomas Gleixner Cc: linux-kernel@vger.kernel.org, x86@kernel.org, Dave Hansen , Borislav Petkov , Ingo Molnar , Nadav Amit , stable@vger.kernel.org, "Peter Zijlstra (Intel)" , "Steven Rostedt (Google)" Subject: [PATCH] x86/alternative: fix race in try_get_desc() Date: Tue, 20 Sep 2022 22:47:43 +0000 Message-Id: <20220920224743.3089-1-namit@vmware.com> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=1.3 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE, RCVD_IN_SBL_CSS,SPF_HELO_NONE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Nadav Amit The text poke mechanism claims to have an RCU-like behavior, but it does not appear that there is any quiescent state to ensure that nobody holds reference to desc. As a result, the following race appears to be possible, which can lead to memory corruption. CPU0 CPU1 ---- ---- text_poke_bp_batch() -> smp_store_release(&bp_desc, &desc) [ notice that desc is on the stack ] poke_int3_handler() [ int3 might be kprobe's so sync events are do not help ] -> try_get_desc(descp=&bp_desc) desc = __READ_ONCE(bp_desc) if (!desc) [false, success] WRITE_ONCE(bp_desc, NULL); atomic_dec_and_test(&desc.refs) [ success, desc space on the stack is being reused and might have non-zero value. ] arch_atomic_inc_not_zero(&desc->refs) [ might succeed since desc points to stack memory that was freed and might be reused. ] I encountered some occasional crashes of poke_int3_handler() when kprobes are set, while accessing desc->vec. The analysis has been done offline and I did not corroborate the cause of the crashes. Yet, it seems that this race might be the root cause. Fix this issue with small backportable patch. Instead of trying to make RCU-like behavior for bp_desc, just eliminate the unnecessary level of indirection of bp_desc, and hold the whole descriptor on the stack. Anyhow, there is only a single descriptor at any given moment. Fixes: 1f676247f36a4 ("x86/alternatives: Implement a better poke_int3_handler() completion scheme" Cc: stable@vger.kernel.org Cc: "Peter Zijlstra (Intel)" Cc: "Steven Rostedt (Google)" Signed-off-by: Nadav Amit --- arch/x86/kernel/alternative.c | 42 +++++++++++++++++------------------ 1 file changed, 20 insertions(+), 22 deletions(-) diff --git a/arch/x86/kernel/alternative.c b/arch/x86/kernel/alternative.c index 62f6b8b7c4a5..4265c9426374 100644 --- a/arch/x86/kernel/alternative.c +++ b/arch/x86/kernel/alternative.c @@ -1319,18 +1319,15 @@ struct bp_patching_desc { atomic_t refs; }; -static struct bp_patching_desc *bp_desc; +static struct bp_patching_desc bp_desc; static __always_inline -struct bp_patching_desc *try_get_desc(struct bp_patching_desc **descp) +struct bp_patching_desc *try_get_desc(void) { - /* rcu_dereference */ - struct bp_patching_desc *desc = __READ_ONCE(*descp); - - if (!desc || !arch_atomic_inc_not_zero(&desc->refs)) + if (!arch_atomic_inc_not_zero(&bp_desc.refs)) return NULL; - return desc; + return &bp_desc; } static __always_inline void put_desc(struct bp_patching_desc *desc) @@ -1367,15 +1364,15 @@ noinstr int poke_int3_handler(struct pt_regs *regs) /* * Having observed our INT3 instruction, we now must observe - * bp_desc: + * bp_desc with non-zero refcount: * - * bp_desc = desc INT3 + * bp_desc.refs = 1 INT3 * WMB RMB - * write INT3 if (desc) + * write INT3 if (bp_desc.refs != 0) */ smp_rmb(); - desc = try_get_desc(&bp_desc); + desc = try_get_desc(); if (!desc) return 0; @@ -1460,18 +1457,21 @@ static int tp_vec_nr; */ static void text_poke_bp_batch(struct text_poke_loc *tp, unsigned int nr_entries) { - struct bp_patching_desc desc = { - .vec = tp, - .nr_entries = nr_entries, - .refs = ATOMIC_INIT(1), - }; unsigned char int3 = INT3_INSN_OPCODE; unsigned int i; int do_sync; lockdep_assert_held(&text_mutex); - smp_store_release(&bp_desc, &desc); /* rcu_assign_pointer */ + bp_desc.vec = tp; + bp_desc.nr_entries = nr_entries; + + /* + * Corresponds to the implicit memory barrier in try_get_desc() to + * ensure reading a non-zero refcount provides up to date bp_desc data. + */ + smp_wmb(); + atomic_set(&bp_desc.refs, 1); /* * Corresponding read barrier in int3 notifier for making sure the @@ -1559,12 +1559,10 @@ static void text_poke_bp_batch(struct text_poke_loc *tp, unsigned int nr_entries text_poke_sync(); /* - * Remove and synchronize_rcu(), except we have a very primitive - * refcount based completion. + * Remove and wait for refs to be zero. */ - WRITE_ONCE(bp_desc, NULL); /* RCU_INIT_POINTER */ - if (!atomic_dec_and_test(&desc.refs)) - atomic_cond_read_acquire(&desc.refs, !VAL); + if (!atomic_dec_and_test(&bp_desc.refs)) + atomic_cond_read_acquire(&bp_desc.refs, !VAL); } static void text_poke_loc_init(struct text_poke_loc *tp, void *addr, -- 2.34.1