Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH] Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del()
From:   patchwork-bot+bluetooth@kernel.org
Message-Id: <166603861674.10129.97922978333278137.git-patchwork-notify@kernel.org>
Date:   Mon, 17 Oct 2022 20:30:16 +0000
References: <20221017075813.6071-1-shaozhengchao@huawei.com>
In-Reply-To: <20221017075813.6071-1-shaozhengchao@huawei.com>
To:     Zhengchao Shao <shaozhengchao@huawei.com>
Cc:     linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org,
        davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
        pabeni@redhat.com, marcel@holtmann.org, johan.hedberg@gmail.com,
        luiz.dentz@gmail.com, weiyongjun1@huawei.com, yuehaibing@huawei.com
Precedence: bulk

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Mon, 17 Oct 2022 15:58:13 +0800 you wrote:
> When l2cap_recv_frame() is invoked to receive data, and the cid is
> L2CAP_CID_A2MP, if the channel does not exist, it will create a channel.
> However, after a channel is created, the hold operation of the channel
> is not performed. In this case, the value of channel reference counting
> is 1. As a result, after hci_error_reset() is triggered, l2cap_conn_del()
> invokes the close hook function of A2MP to release the channel. Then
>  l2cap_chan_unlock(chan) will trigger UAF issue.
> 
> [...]

Here is the summary with links:
  - Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del()
    https://git.kernel.org/bluetooth/bluetooth-next/c/42cf46dea905

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html