From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 D75A43F12C8 for ; Sat, 15 Aug 2026 12:31:59 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786797121; cv=none; b=IRYiNNGmICU86BisuaHTjJajW6OL53saWFjxEqolWJEdbVVTQ9udThGZJ+XFbFjNGqd2kkeXCCluyVNgR97tGpXxVZ8nTga2yXwcypLDBEAkHFxZRhD3Kshvamwr/CPaL4cVpuFNp9fEMLjV0DUUHc8ATlQp3GPVcofHS+lcEpM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786797121; c=relaxed/simple; bh=+ELi0G6aMIj0NEph9GbfSntDWQCi3CKskb2ZvgrLhzM=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=s4tVb7i6JAT4eIP5aFUCXjRHTYoVKdW6bmuDF4y6F6AJPkD3+YTZkSMBvQvGvUHR9AcMGPjueBCm0e63hfUJSkIqrKmbmr40dcaAUnGtXodFmKmiq/40MfAeK0+RGgCEeJX3RU5rM3Ew+yl0dF+e3/bVf7Vk1KqaNlpt+LW4/m4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=MQAttpLm; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="MQAttpLm" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3D2951F000E9; Sat, 15 Aug 2026 12:31:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1786797119; bh=EWhJX4DcOlIV5aCPwU5S7fwi9k3qYiyJP1p6eF2e00E=; h=From:To:Cc:Subject:Date:Reply-To; b=MQAttpLmLKkZmCD1sUo4/iOafDqRwKCFk3SQKyZWk08Ns/7Uys5+AWCgLKyoUES1B 1Yjkv7bSZmWcVFl2zkCg98zqqKAhW6RwvqT0xnxEBCvi67hbNwfxiPKdqaQ2HqJDLh xNVEk83+gV+XyeIgp9ZAfIheEax8vzyYXmGmt3vI= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-74536: Bluetooth: ISO: fix leaking sk after socket release Date: Sat, 15 Aug 2026 21:26:57 +0900 Message-ID: <2026081547-CVE-2026-74536-9ef7@gregkh> X-Mailer: git-send-email 2.55.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=3013; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=t/kzG6J6mnKnzMOdqIHyHfjBQ237pg6IdrjThr5spPs=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkNUacV9k0+d878f3XBco5ki3Oe3zm3ZPttfGnan9CZZ rJA4rVKRywLgyATg6yYIsuXbTxH91ccUvQytD0NM4eVCWQIAxenAEykIp5hfvhybVsf77kzZL+e u/lGxliHNVjWmWHBtty2qBd/xXON60XN448el/Fw+5sJAA== 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: ISO: fix leaking sk after socket release iso_sock_kill() tests !sock_flag(sk, SOCK_ZAPPED) || sk->sk_socket || sock_flag(sk, SOCK_DEAD) for early return, but this is always true since sock_orphan(sk) sets SOCK_DEAD, so the sk reference released by socket always leaks, iso_sock_destruct is never called. The socket reference also leaks when __iso_sock_close() does not set SOCK_ZAPPED, since iso_conn_del() does not call iso_sock_kill() after zapping. Fix by replacing SOCK_DEAD by BT_SK_KILLED flag that is not used for something else, and lock_sock to ensure iso_sock_kill() puts sk only after socket release only once. Release and iso_conn_del may run concurrently. Call iso_sock_kill() from iso_conn_del() to clean sk up after zapping. Remove call to iso_sock_kill() from iso_sock_close(), as it's generally no-op there. The Linux kernel CVE team has assigned CVE-2026-74536 to this issue. Affected and fixed versions =========================== Issue introduced in 6.0 with commit ccf74f2390d60a2f9a75ef496d2564abb478f46a and fixed in 6.12.103 with commit 96ed3c772c08e7a91c399567f412618e43231023 Issue introduced in 6.0 with commit ccf74f2390d60a2f9a75ef496d2564abb478f46a and fixed in 6.18.44 with commit e76a0ae6542ae43241b2147bacf4990e7ae5316a Issue introduced in 6.0 with commit ccf74f2390d60a2f9a75ef496d2564abb478f46a and fixed in 7.1.8 with commit e30e5ca63c8fbe3cd505fbb419bb547760cda633 Issue introduced in 6.0 with commit ccf74f2390d60a2f9a75ef496d2564abb478f46a and fixed in 7.2-rc6 with commit ce57442a379212fe3fda59c9437ee8217eceb5b1 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-2026-74536 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/iso.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/96ed3c772c08e7a91c399567f412618e43231023 https://git.kernel.org/stable/c/e76a0ae6542ae43241b2147bacf4990e7ae5316a https://git.kernel.org/stable/c/e30e5ca63c8fbe3cd505fbb419bb547760cda633 https://git.kernel.org/stable/c/ce57442a379212fe3fda59c9437ee8217eceb5b1