Received: by 2002:a05:6a10:c604:0:0:0:0 with SMTP id y4csp195119pxt; Wed, 4 Aug 2021 08:53:47 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzrkOKqRKm9BiK1bbMN00GfNWmVRReeiRnY0bFrSS9ZWC104FnXubTUSbXMPmFqN84WVcdQ X-Received: by 2002:a17:907:1106:: with SMTP id qu6mr26340763ejb.455.1628092427418; Wed, 04 Aug 2021 08:53:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1628092427; cv=none; d=google.com; s=arc-20160816; b=a/PyCX1RFjyMqgA5NbXigiMl+a4z50kgoYid7yIuA0tjYn7De1eKqAoW12F9SnrBy8 +tIwuILch6GlY7IaqB4kQhtSSXa7IzCWG5TA0cHKk7jQRjzQXICwZS0zkg/cIcIffGPX rqKpz7SjRkjj9fScixNUx9eCbTLrOM/OD/y49gP1OnYA6myYJvQOZe43NYT2BT1Uh256 Vx283cHaGxKN2xTlQuuU+P71VzP2g0IIEtV7lehdRHKzm+vUtHUSgw7cYg6FA8KrUHsy E3Lb4ey3KGesiVaJbv6HutlP2x0Cb9vW3zkLOVmPESp/DH+UzvHM9BIViq5ZU4lqFjnZ Vj7Q== 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 :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=zIRbv5ZXxIid872Ol8a8JiBpz6JG4aviAWXZnPlaMDM=; b=VfmknONL3D1MhH2RsnzD9J94ZcjYOjQLXnsL3lB3DUZXM+dwmpw+rTvR/1J+ZFfAFi w23fVYNnmZy2QA6RsZTSO223MzFuUGh+ulHquZJ1dSygI9z/uE/WxFvquHCePu8+t4tZ b7FmmRbbyXfI00k7mM4HvbCTy7xEg4Cxuz1WWT5iMRcwpZpQudn10/nop44jKMWKR07V FhtwFdPT1BHJK/no6232WKg3CGgscjXdcrFQSxRxMcyInI/TkYhAZov2Ys6IlvqofuDJ kuoQK7Jtp2OCSIf1pAffEyPoRG/wsacv+QMefc1/nTp7YUUZR9pKcMSHApPyI2VBJTiR MIqQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=rdJHyKNk; 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=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id z18si2528940ejw.561.2021.08.04.08.53.23; Wed, 04 Aug 2021 08:53:47 -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=@gmail.com header.s=20161025 header.b=rdJHyKNk; 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=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239523AbhHDPuP (ORCPT + 99 others); Wed, 4 Aug 2021 11:50:15 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45386 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239555AbhHDPtX (ORCPT ); Wed, 4 Aug 2021 11:49:23 -0400 Received: from mail-pj1-x1032.google.com (mail-pj1-x1032.google.com [IPv6:2607:f8b0:4864:20::1032]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4676AC0617A0; Wed, 4 Aug 2021 08:48:59 -0700 (PDT) Received: by mail-pj1-x1032.google.com with SMTP id pj14-20020a17090b4f4eb029017786cf98f9so4189184pjb.2; Wed, 04 Aug 2021 08:48:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=zIRbv5ZXxIid872Ol8a8JiBpz6JG4aviAWXZnPlaMDM=; b=rdJHyKNkVdzEDu+i17BA0ESSeSHw7WdgDcmPzNzHC5dNA/1Da4om9QYVZAQ4eTNOjp nE7CuugZzapfrdXloo+i/YUsSvvhPFb8bL/XF5p6FrBQ0OqA2vxwuuZ2sM5q1vxRpRue n0O0otg/gigaHc2qifkS2eW1v/eG19WJXQ/iS+t6g1Esnq/NqkYKxcYuQjkLbTq/6COt CAuJtvNvD3qolCfKL0fDxxGKxq6BLmjxxVeIP6P1H1GHP9ukH7cFRBxdeCgh2Iv4T8tC ukT5oftekjWfwOTmCOFM6YyyGyTXX/3a8wSbvliCRkgp6dtFCLUCCTzM5CrqfO7m9XU5 Do0A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=zIRbv5ZXxIid872Ol8a8JiBpz6JG4aviAWXZnPlaMDM=; b=ersTFvuKsw/bo1mk+TXK65cmFfXMPrBNu8rOsAQYYVLdh5iztpnZpocGq1Mi5F8B36 dTSrT5AinLzXTrRanJuI85MjCSlJi1nGCLCi0Sr+TZLn8gA8UjyPnzH8JNVf8cO0CyZs m5Fm+HzReU9yEsQ2tMcJe7pbIT81dTcpzWo4u2dUn2lgF2SZPBMCkcs97yR5zUNEMarX /g9zNBQI9kQ01IBVVxPoKqzaYZZOGx+oWaSbTmZ17m2JcqNNqYWIC17pYIGpSnpx4i0x cUur+GW5D9t15+f/tFfuMsjLNHSNBe8tv+baWHoX7y5QiOj5oqOdnD5OJFhiw0FVTozV uKIA== X-Gm-Message-State: AOAM531hyo+muHu7o/2QdNqD4dyaiVxZQU2dvbDGvfPyLgyf0sI+hKot OXaQaZ8/Ny5z3HLt9Ph2yjg= X-Received: by 2002:a17:90a:bd18:: with SMTP id y24mr10513325pjr.83.1628092138838; Wed, 04 Aug 2021 08:48:58 -0700 (PDT) Received: from localhost.localdomain ([118.200.190.93]) by smtp.gmail.com with ESMTPSA id b15sm4007274pgj.60.2021.08.04.08.48.55 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 04 Aug 2021 08:48:58 -0700 (PDT) From: Desmond Cheong Zhi Xi To: marcel@holtmann.org, johan.hedberg@gmail.com, luiz.dentz@gmail.com, davem@davemloft.net, kuba@kernel.org, sudipm.mukherjee@gmail.com Cc: Desmond Cheong Zhi Xi , linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, skhan@linuxfoundation.org, gregkh@linuxfoundation.org, linux-kernel-mentees@lists.linuxfoundation.org Subject: [RESEND PATCH v5 6/6] Bluetooth: fix repeated calls to sco_sock_kill Date: Wed, 4 Aug 2021 23:47:12 +0800 Message-Id: <20210804154712.929986-7-desmondcheongzx@gmail.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20210804154712.929986-1-desmondcheongzx@gmail.com> References: <20210804154712.929986-1-desmondcheongzx@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org In commit 4e1a720d0312 ("Bluetooth: avoid killing an already killed socket"), a check was added to sco_sock_kill to skip killing a socket if the SOCK_DEAD flag was set. This was done after a trace for a use-after-free bug showed that the same sock pointer was being killed twice. Unfortunately, this check prevents sco_sock_kill from running on any socket. sco_sock_kill kills a socket only if it's zapped and orphaned, however sock_orphan announces that the socket is dead before detaching it. i.e., orphaned sockets have the SOCK_DEAD flag set. To fix this, we remove the check for SOCK_DEAD, and avoid repeated calls to sco_sock_kill by removing incorrect calls in: 1. sco_sock_timeout. The socket should not be killed on timeout as further processing is expected to be done. For example, sco_sock_connect sets the timer then waits for the socket to be connected or for an error to be returned. 2. sco_conn_del. This function should clean up resources for the connection, but the socket itself should be cleaned up in sco_sock_release. 3. sco_sock_close. Calls to sco_sock_close in sco_sock_cleanup_listen and sco_sock_release are followed by sco_sock_kill. Hence the duplicated call should be removed. Fixes: 4e1a720d0312 ("Bluetooth: avoid killing an already killed socket") Signed-off-by: Desmond Cheong Zhi Xi --- net/bluetooth/sco.c | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/net/bluetooth/sco.c b/net/bluetooth/sco.c index 418543c390b3..cf43ccb50573 100644 --- a/net/bluetooth/sco.c +++ b/net/bluetooth/sco.c @@ -97,8 +97,6 @@ static void sco_sock_timeout(struct work_struct *work) sk->sk_err = ETIMEDOUT; sk->sk_state_change(sk); release_sock(sk); - - sco_sock_kill(sk); sock_put(sk); } @@ -203,7 +201,6 @@ static void sco_conn_del(struct hci_conn *hcon, int err) sco_sock_clear_timer(sk); sco_chan_del(sk, err); release_sock(sk); - sco_sock_kill(sk); sock_put(sk); /* Ensure no more work items will run before freeing conn. */ @@ -410,8 +407,7 @@ static void sco_sock_cleanup_listen(struct sock *parent) */ static void sco_sock_kill(struct sock *sk) { - if (!sock_flag(sk, SOCK_ZAPPED) || sk->sk_socket || - sock_flag(sk, SOCK_DEAD)) + if (!sock_flag(sk, SOCK_ZAPPED) || sk->sk_socket) return; BT_DBG("sk %p state %d", sk, sk->sk_state); @@ -463,7 +459,6 @@ static void sco_sock_close(struct sock *sk) sco_sock_clear_timer(sk); __sco_sock_close(sk); release_sock(sk); - sco_sock_kill(sk); } static void sco_skb_put_cmsg(struct sk_buff *skb, struct msghdr *msg, -- 2.25.1