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 622BC374A08 for ; Sun, 18 Oct 2026 15:18:30 +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=1792336711; cv=none; b=hKSlwKvk3xVCIvAC7Diw85d7jdlvv1Hcs6rM/eM3DAdaoQC+zFNqWe9ZIgfz62/hdLd+U6SVMVTUvDtePJg4L3j3Xw0phXplbtod2l2jpmy5vEKuXCDly8RnUkrg7bMP3+8LgdAqrPjIoDBf8qZ68gilArfd5EKlL6gy2Oz5SeI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1792336711; c=relaxed/simple; bh=zxsoGEzmN7vFhr+PTu+cQTtQ6kYl5LCEEJIuq6Cj6SU=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=bnhPdujrGNR2xDhbaGIHEp/0ZyyH2WQhBWJfxt42XNJRCOXVI5/SaOxyFz0AnN3P2Q+inQsMXeH6V2yFWYO/TZcgon5GAT5uwescBcZtkUTpeXAzxfPW8oGvFj0/I53UrPztZWYQjML8kalu90ZT4NiMs58dRttojlkHU8gjMd8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=0O3LfZsJ; 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="0O3LfZsJ" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6D6C91F000C4; Sun, 18 Oct 2026 15:18:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1792336710; bh=Ldb96CTyrHSHhfCR1WBzPVTSK+utnue+X6QmvfM5HtE=; h=From:To:Cc:Subject:Date:Reply-To; b=0O3LfZsJONTaGDSRD/5tEpunOUj+CakgJOquR4X4Bx0AgKQEPwxmlpnnId+BisJ6O hV7r0cy0g8fcxX80UJZy1PSKcqk+WaFjckqVHDYUSooFyy9PZa8H508YZfHHxpeF5r 4GNIDVBxYcFfzGYjRpzOdnbsEapQd/PtHnsTE4q8= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-98456: Bluetooth: mgmt: fix race in read_unconf_index_list() Date: Sun, 18 Oct 2026 17:15:20 +0200 Message-ID: <2026101809-CVE-2026-98456-2b09@gregkh> X-Mailer: git-send-email 2.56.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=3229; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=Fyl06cjJJdvmRw/QUGonK7OytmHMlnd2hLMW0ygA7KQ=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlXHtW5GDftPB76YLLk4YP3n32b1ykbxbCrpKE2TSM1r OvYkrUlHbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAjCRmx8ZFsx5FfGl622eyoyF 9dlRmhvPbe35e41hwZU3ym8ZKzpmO/xc6VLh6BNhoRq8CAA= 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: mgmt: fix race in read_unconf_index_list() read_unconf_index_list() counts unconfigured controllers before allocating its response, then checks the device flags again while filling it. hci_dev_list_lock stabilizes list membership, but it does not serialize the per-device flags. During asynchronous controller setup, the worker can set HCI_UNCONFIGURED and clear HCI_SETUP between the two passes. A controller omitted from the allocation count can then become eligible for the fill pass, causing an out-of-bounds write to rp->index[]. Allocate space for every device on hci_dev_list. Since list membership cannot change while hci_dev_list_lock is held, the response remains large enough regardless of flag transitions. The reported count and response length still include only eligible unconfigured controllers. The Linux kernel CVE team has assigned CVE-2026-98456 to this issue. Affected and fixed versions =========================== Issue introduced in 3.17 with commit 73d1df2a7a1036a1f000e5f0ece6ade3e082b854 and fixed in 6.6.158 with commit 524e0450dd9a396f99a81b045219b0e2ea0dab57 Issue introduced in 3.17 with commit 73d1df2a7a1036a1f000e5f0ece6ade3e082b854 and fixed in 6.12.112 with commit 8ddf962c76432a10a6cb80042875cbc48a9c056b Issue introduced in 3.17 with commit 73d1df2a7a1036a1f000e5f0ece6ade3e082b854 and fixed in 6.18.55 with commit 416546cd6a54e9b68f2b91bc680b1ee17dcd77a1 Issue introduced in 3.17 with commit 73d1df2a7a1036a1f000e5f0ece6ade3e082b854 and fixed in 7.2.9 with commit 2e8bba0360d1379bfa8da47c8f5dadbb10a3fba1 Issue introduced in 3.17 with commit 73d1df2a7a1036a1f000e5f0ece6ade3e082b854 and fixed in 7.3-rc5 with commit b5dbb41b212c50c095a4dbee3017a84fe94f033b 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-98456 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/mgmt.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/524e0450dd9a396f99a81b045219b0e2ea0dab57 https://git.kernel.org/stable/c/8ddf962c76432a10a6cb80042875cbc48a9c056b https://git.kernel.org/stable/c/416546cd6a54e9b68f2b91bc680b1ee17dcd77a1 https://git.kernel.org/stable/c/2e8bba0360d1379bfa8da47c8f5dadbb10a3fba1 https://git.kernel.org/stable/c/b5dbb41b212c50c095a4dbee3017a84fe94f033b