From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 0896734DCC4 for ; Tue, 16 Dec 2025 15:08:02 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1765897682; cv=none; b=DgiChADjdhAMCm1Uh0HmsVOTElMMpCUOw/+4LMQvqUY5gIz9NcesaRHXQGCvhtea+u0bpobfljIX1e/C3r4Pxpj7V/vMzCJ9NPejkqN4pbV37Hk4j8qKGTuI86wiFP9odu3g9sUC/DKS1bSRa6fE1ztAhiGOJmDxQ05QKb9tKLs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1765897682; c=relaxed/simple; bh=ANbZ5DM22g2RkRomKZBS6MIbdAsz9AV9b0N4p+ScCsc=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=FTu72HhmH32v2lhtmNDFO4RHCzEnXJ6QhOCAthReDZD0B09POrRhmViFgTCgnJR2W4sp3PVuZGSHvjVXVVf3wPtodDcdUp+z6Cn+LtlUWg5Om5lNEqI/JpoVOkyvRckzj9vqT2la6upMe5dXUUZP9kPkK/m+MVnnLwz0oPVANpM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=XVIB0s8P; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="XVIB0s8P" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 7DB80C4CEF5; Tue, 16 Dec 2025 15:08:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1765897681; bh=ANbZ5DM22g2RkRomKZBS6MIbdAsz9AV9b0N4p+ScCsc=; h=From:To:Cc:Subject:Date:Reply-To:From; b=XVIB0s8PCOR6V5XoGWdDJNFw71mOezcwIggrqZQb6tDya9F9xpjO12jLCy2BVIQs/ 0/99bX0K9EA/saKKzBryh8emfgD31mgS6qHWYlfzFg0h5ZCq9gnGDbbFxPGgKbAzt4 ff+JASRJn1PvPu2Z4HMH/do1LMwwVSEhSp01gLeQ= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2025-68305: Bluetooth: hci_sock: Prevent race in socket write iter and sock bind Date: Tue, 16 Dec 2025 16:06:59 +0100 Message-ID: <2025121644-CVE-2025-68305-e40b@gregkh> X-Mailer: git-send-email 2.52.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=3855; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=vRft7x6IB5X+ufYuFjDaYgPSs6Jugg/FN8rHbrPpWCs=; b=owGbwMvMwCRo6H6F97bub03G02pJDJmOpS0z2j3ntr0Rqn9sPIfTS8gj/LMyT88nVd8tu9bsT cxg/67dEcvCIMjEICumyPJlG8/R/RWHFL0MbU/DzGFlAhnCwMUpABORkmCYHxCsl/xn/ysHS8XF s82OT8y/o1KrwTBXsr++wZG128A7YnFiUuc3eYHQy8sA X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman Description =========== In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sock: Prevent race in socket write iter and sock bind There is a potential race condition between sock bind and socket write iter. bind may free the same cmd via mgmt_pending before write iter sends the cmd, just as syzbot reported in UAF[1]. Here we use hci_dev_lock to synchronize the two, thereby avoiding the UAF mentioned in [1]. [1] syzbot reported: BUG: KASAN: slab-use-after-free in mgmt_pending_remove+0x3b/0x210 net/bluetooth/mgmt_util.c:316 Read of size 8 at addr ffff888077164818 by task syz.0.17/5989 Call Trace: mgmt_pending_remove+0x3b/0x210 net/bluetooth/mgmt_util.c:316 set_link_security+0x5c2/0x710 net/bluetooth/mgmt.c:1918 hci_mgmt_cmd+0x9c9/0xef0 net/bluetooth/hci_sock.c:1719 hci_sock_sendmsg+0x6ca/0xef0 net/bluetooth/hci_sock.c:1839 sock_sendmsg_nosec net/socket.c:727 [inline] __sock_sendmsg+0x21c/0x270 net/socket.c:742 sock_write_iter+0x279/0x360 net/socket.c:1195 Allocated by task 5989: mgmt_pending_add+0x35/0x140 net/bluetooth/mgmt_util.c:296 set_link_security+0x557/0x710 net/bluetooth/mgmt.c:1910 hci_mgmt_cmd+0x9c9/0xef0 net/bluetooth/hci_sock.c:1719 hci_sock_sendmsg+0x6ca/0xef0 net/bluetooth/hci_sock.c:1839 sock_sendmsg_nosec net/socket.c:727 [inline] __sock_sendmsg+0x21c/0x270 net/socket.c:742 sock_write_iter+0x279/0x360 net/socket.c:1195 Freed by task 5991: mgmt_pending_free net/bluetooth/mgmt_util.c:311 [inline] mgmt_pending_foreach+0x30d/0x380 net/bluetooth/mgmt_util.c:257 mgmt_index_removed+0x112/0x2f0 net/bluetooth/mgmt.c:9477 hci_sock_bind+0xbe9/0x1000 net/bluetooth/hci_sock.c:1314 The Linux kernel CVE team has assigned CVE-2025-68305 to this issue. Affected and fixed versions =========================== Issue introduced in 6.6.94 with commit bdd56875c6926d8009914f427df71797693e90d4 and fixed in 6.6.119 with commit fe68510fc99bb4b88c9c611f83699749002d515a Issue introduced in 6.12.34 with commit 4e83f2dbb2bf677e614109df24426c4dded472d4 and fixed in 6.12.61 with commit e90c05fc5bbea956450a05cc3b36b8fa29cf195e Issue introduced in 6.16 with commit 6fe26f694c824b8a4dbf50c635bee1302e3f099c and fixed in 6.17.11 with commit 69fcb0344bc0dd5b13d7e4e98f8b6bf25a6d4ff7 Issue introduced in 6.16 with commit 6fe26f694c824b8a4dbf50c635bee1302e3f099c and fixed in 6.18 with commit 89bb613511cc21ed5ba6bddc1c9b9ae9c0dad392 Issue introduced in 6.15.3 with commit d7882db79135c829a922daf3571f33ea1e056ae3 Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2025-68305 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: net/bluetooth/hci_sock.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/fe68510fc99bb4b88c9c611f83699749002d515a https://git.kernel.org/stable/c/e90c05fc5bbea956450a05cc3b36b8fa29cf195e https://git.kernel.org/stable/c/69fcb0344bc0dd5b13d7e4e98f8b6bf25a6d4ff7 https://git.kernel.org/stable/c/89bb613511cc21ed5ba6bddc1c9b9ae9c0dad392