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 387804B203E for ; Fri, 4 Sep 2026 15:14:51 +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=1788534893; cv=none; b=Y6CkDQKVHefpswc41u4xBj05ZJ/xm0GI3fk4x+7yInRyN4iWK98/9MccUyLzw6QJYhFix2boyB2mYjIYRcvqPf8osHOQUumF7lmp0NVrA3Wpnrtt2J8Eta6e3E1bL+lpLCxKPnNM1RSnEpVPT565JzTp5XgqskmbpC5fcAR8V7Q= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1788534893; c=relaxed/simple; bh=iOxyAXlrgxE6DeGTfMJOpcEgV7TGcTgH1YD2EhnQQBk=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=QamB0c5iS2SgEbTvAoPSH49xYZqxLYuQI+PWdqxvLPRagQnpCiYyIUR4d0OqKq9IlEUxRCJBV47xnjFpYxLI/Bn+GjPGovt9wjmSewSB+D/myg9CQpG7tWZ9VjY1kz2GjJwxbvLUD9yR1fdmILifwPGcgLsKrWn2rd4O5mhON1M= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=SXyBaNXy; 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="SXyBaNXy" Received: by smtp.kernel.org (Postfix) with ESMTPSA id E06401F00AC4; Fri, 4 Sep 2026 15:14:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1788534891; bh=jeu79GFV/0JZPBqCpomz0bgO+36QQi0BRXySfq/Ivx8=; h=From:To:Cc:Subject:Date:Reply-To; b=SXyBaNXysktNe3qxR0tTdb2S44KdmkLjUDVCLuJKPGp/2cMKaPuYKC9rwlLjqfCkZ Sa56TthoThhH2Z27zFje/kJrCcjB2nk1N8p1Nd85ay4Kh5m4Trgd7GHzjLBbczWOk5 NUfJaQEhrz0ZLRX+ASzJT4UxrzjVhM6O6fYYiO0Y= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-80760: Bluetooth: MGMT: reject HCI_CMD_SYNC params_len above 255 Date: Fri, 4 Sep 2026 17:10:59 +0200 Message-ID: <2026090459-CVE-2026-80760-a01f@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=3246; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=UZUqeSeppscYZxFSpOIhkWnUDsU2uWwLXnwpae/nBPQ=; b=owGbwMvMwCRo6H6F97bub03G02pJDFmz7jdr2il2ey/NnDfr25Kg0w0muzrXFPtmbFSx2391t ve5SYUCHbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAjCRAGOG+SGmPSxzUjJ6pFbV PJZ1NropbMqWzLDgoJZ6S3HSz3iZrbJp7w6nL0x6PkUNAA== 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: reject HCI_CMD_SYNC params_len above 255 mgmt_hci_cmd_sync() checks that the message length agrees with params_len but puts no upper bound on it. params_len is __le16 while the parameter length in the HCI command header is a u8: struct hci_command_hdr { __le16 opcode; __u8 plen; } __packed; hci_cmd_sync_alloc() assigns one to the other: hdr->plen = plen; if (plen) skb_put_data(skb, param, plen); so a params_len of 256 leaves plen at 0 while all 256 bytes are still appended. The frame handed to the driver then declares no parameters and carries 256 of them. On a length framed transport such as H:4 the controller takes the trailing bytes as the start of the next packet. The mgmt socket MTU is HCI_MAX_FRAME_SIZE, so params_len can reach about 1KB this way. Commit 03f1700b9b4d ("Bluetooth: MGMT: reject malformed HCI_CMD_SYNC commands") only made params_len agree with the message length, a value that fits the message but not the header field is still accepted. Reject params_len that does not fit the header field. The Linux kernel CVE team has assigned CVE-2026-80760 to this issue. Affected and fixed versions =========================== Issue introduced in 6.13 with commit 827af4787e74e8df9e8e0677a69fbb15e0856d2f and fixed in 6.18.47 with commit b7d9edcf9fe6e9ec3a2e80ef9e8d44ef9b4f2894 Issue introduced in 6.13 with commit 827af4787e74e8df9e8e0677a69fbb15e0856d2f and fixed in 7.1.11 with commit 0bd0195ce25737cbdd0eabc54319ee0ddf3a0ad2 Issue introduced in 6.13 with commit 827af4787e74e8df9e8e0677a69fbb15e0856d2f and fixed in 7.2.1 with commit 6e1c44878aa3ee7336efeaf01414b030b0a5c273 Issue introduced in 6.13 with commit 827af4787e74e8df9e8e0677a69fbb15e0856d2f and fixed in 7.3-rc1 with commit 5d95286b6d6e8f1d304da7522bfa6860fc017e48 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-80760 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/b7d9edcf9fe6e9ec3a2e80ef9e8d44ef9b4f2894 https://git.kernel.org/stable/c/0bd0195ce25737cbdd0eabc54319ee0ddf3a0ad2 https://git.kernel.org/stable/c/6e1c44878aa3ee7336efeaf01414b030b0a5c273 https://git.kernel.org/stable/c/5d95286b6d6e8f1d304da7522bfa6860fc017e48