Received: by 2002:a05:6358:a55:b0:ec:fcf4:3ecf with SMTP id 21csp618899rwb; Fri, 13 Jan 2023 01:59:21 -0800 (PST) X-Google-Smtp-Source: AMrXdXtijjkzAEnoG3cN1V7XvPninmiZQBRPlb1I8mxe1KEjRKlx7GgwQqQ4t2WLy8ZcxLdPCYRh X-Received: by 2002:a17:903:24a:b0:194:480d:6afc with SMTP id j10-20020a170903024a00b00194480d6afcmr11326110plh.48.1673603960975; Fri, 13 Jan 2023 01:59:20 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1673603960; cv=none; d=google.com; s=arc-20160816; b=P3KWZME8mH7gVxtAa+hr/SBV4VwjSsuoACWpNBVI7Ts1ASokQxa6nCIWMqlbbqlnBQ b8kDX+8mPPs0P40+4gugrBJvWT2H4azL9Pp3H5sZQO6irfAKmX8ZuyZDuHRjKdr747// PAxxjkMkkN7TeMjzLDbJVB0u5M66ISuW9lsFgkoY7Iwhsx9lkcTpMC31K5NqHxoq4d7X GoqQ7GIZZocZgM/6bxcXONV1Tel6WlxKlc8WdJ0E4yF/ascfXw7qCsLOJWRQjDOq3F+4 fvJvo9X1lXmji/l0KuNzuxQagTHQa/xpe+befuihdbMXy8ZV7l01T6fQR1zIe7vP87ps A6Nw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature :dkim-signature; bh=wuNY130VcsaJBRLFnePwzZuLqGqTZv2d6U87GrUaNAQ=; b=vi0V0Y+KewCrTA6C3dODXEhzRIBUbD1JNJSiPq9pM9YDgDZXuvngE28/iZAPdMLbty PafMveW2MYtTbhYNXpF5HyP5QKtWDbAWtOIYqQqGvLxNYoW4xb7Y8GYISP91/Vit4oFa eMalzZAlq5iiMCDeiOep/xSUgpuRCZp162SR9MbsF4PH1pJj5Q27W3DjV9Tw0za2V0uo BgZi48V6XERDKycbdrMq/Kxxzfn4BOmyOJ6IZe8lfYM+ywOKIHij3IT4ktdDE5oChJKl MFwcj/DVSWV94YLVt1OINAiZsEqB/AHi9ndc1IcMJ3Wbzggfe7NJzglQy06nmqgAILsV lOeA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.cz header.s=susede2_rsa header.b=hgoGZy+T; dkim=neutral (no key) header.i=@suse.cz header.s=susede2_ed25519; 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 Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id e7-20020a170903240700b0019475289415si437281plo.85.2023.01.13.01.59.14; Fri, 13 Jan 2023 01:59:20 -0800 (PST) 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=@suse.cz header.s=susede2_rsa header.b=hgoGZy+T; dkim=neutral (no key) header.i=@suse.cz header.s=susede2_ed25519; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231327AbjAMJwf (ORCPT + 51 others); Fri, 13 Jan 2023 04:52:35 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41768 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234084AbjAMJv7 (ORCPT ); Fri, 13 Jan 2023 04:51:59 -0500 Received: from smtp-out1.suse.de (smtp-out1.suse.de [IPv6:2001:67c:2178:6::1c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B565465AF2; Fri, 13 Jan 2023 01:46:31 -0800 (PST) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id 755A0221F8; Fri, 13 Jan 2023 09:46:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1673603189; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=wuNY130VcsaJBRLFnePwzZuLqGqTZv2d6U87GrUaNAQ=; b=hgoGZy+TXMw0Ixd2Wx2SrsMRpA8HVurYPTWkvMq3oFytcppYp8DBAU2G2wYaxZVbpeEdtA IlCXuLkTK1IsWsySsb2YNY9XQmgAHknmcO6wQoRCaSBIXfWXe5S8/m6OMf407WttQPct57 J87uoo4ZwLiGvpIRr3XffsCPEVQdGkI= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1673603189; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=wuNY130VcsaJBRLFnePwzZuLqGqTZv2d6U87GrUaNAQ=; b=IgP2UMdc5EjtUBbApQmhvYatY+seHiqNjbAUkIBBeS8d53XQXHP/orci1x1jWSNtM0p7PV 395NK7p3ubUm7vCg== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 630CB1358A; Fri, 13 Jan 2023 09:46:29 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id QfohGHUowWP8fgAAMHmgww (envelope-from ); Fri, 13 Jan 2023 09:46:29 +0000 Received: by quack3.suse.cz (Postfix, from userid 1000) id D66A0A0744; Fri, 13 Jan 2023 10:46:28 +0100 (CET) Date: Fri, 13 Jan 2023 10:46:28 +0100 From: Jan Kara To: Yu Kuai Cc: jack@suse.cz, tj@kernel.org, josef@toxicpanda.com, axboe@kernel.dk, paolo.valente@linaro.org, shinichiro.kawasaki@wdc.com, cgroups@vger.kernel.org, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, yukuai1@huaweicloud.com, yi.zhang@huawei.com, yangerkun@huawei.com Subject: Re: [PATCH] block, bfq: fix uaf for bfqq in bic_set_bfqq() Message-ID: <20230113094628.foepphisccxjligo@quack3> References: <20230113094410.2907223-1-yukuai3@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230113094410.2907223-1-yukuai3@huawei.com> X-Spam-Status: No, score=-1.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.6 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 On Fri 13-01-23 17:44:10, Yu Kuai wrote: > After commit 64dc8c732f5c ("block, bfq: fix possible uaf for 'bfqq->bic'"), > bic->bfqq will be accessed in bic_set_bfqq(), however, in some context > bic->bfqq will be freed first, and bic_set_bfqq() is called with the freed > bic->bfqq. > > Fix the problem by always freeing bfqq after bic_set_bfqq(). > > Fixes: 64dc8c732f5c ("block, bfq: fix possible uaf for 'bfqq->bic'") > Reported-and-tested-by: Shinichiro Kawasaki > Signed-off-by: Yu Kuai Looks good, thanks for the fix! Feel free to add: Reviewed-by: Jan Kara Honza > --- > block/bfq-cgroup.c | 2 +- > block/bfq-iosched.c | 4 +++- > 2 files changed, 4 insertions(+), 2 deletions(-) > > diff --git a/block/bfq-cgroup.c b/block/bfq-cgroup.c > index a6e8da5f5cfd..feb13ac25557 100644 > --- a/block/bfq-cgroup.c > +++ b/block/bfq-cgroup.c > @@ -749,8 +749,8 @@ static void bfq_sync_bfqq_move(struct bfq_data *bfqd, > * old cgroup. > */ > bfq_put_cooperator(sync_bfqq); > - bfq_release_process_ref(bfqd, sync_bfqq); > bic_set_bfqq(bic, NULL, true, act_idx); > + bfq_release_process_ref(bfqd, sync_bfqq); > } > } > > diff --git a/block/bfq-iosched.c b/block/bfq-iosched.c > index 815b884d6c5a..2ddf831221c4 100644 > --- a/block/bfq-iosched.c > +++ b/block/bfq-iosched.c > @@ -5581,9 +5581,11 @@ static void bfq_check_ioprio_change(struct bfq_io_cq *bic, struct bio *bio) > > bfqq = bic_to_bfqq(bic, false, bfq_actuator_index(bfqd, bio)); > if (bfqq) { > - bfq_release_process_ref(bfqd, bfqq); > + struct bfq_queue *old_bfqq = bfqq; > + > bfqq = bfq_get_queue(bfqd, bio, false, bic, true); > bic_set_bfqq(bic, bfqq, false, bfq_actuator_index(bfqd, bio)); > + bfq_release_process_ref(bfqd, old_bfqq); > } > > bfqq = bic_to_bfqq(bic, true, bfq_actuator_index(bfqd, bio)); > -- > 2.31.1 > -- Jan Kara SUSE Labs, CR