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 52EBE3D3334 for ; Mon, 10 Aug 2026 12:11:12 +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=1786363873; cv=none; b=BuJWvdSYJKgoUtknILDLr8OpnQ2yOycTkpbJRidpjoeA90DWICoxuIm+pRPf9iUnhWjL2RpFUZjDsyBz47BcGNBZ/HP1beesVA0ZPs4BfOTWvM92vmO8/5TbS2lrOA4uURQcLi7iKPLRVA3uGCSJ80A5YyiL6nCwdA5Z/9IiaUk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786363873; c=relaxed/simple; bh=2is8R/tN6tZndZ9L1nUaUyUma5ovALAo+wNJAM0tf7k=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=VP0Qp2oHnHxmb3YEee0Te5MSrkOusYrHN5JWJu/s9ziAHUf7IGdTgZD65oU1ywkDOTnqIjxtRxl4FvFSoUVr5N6IO84ZHYQwY2YRmGU5+/jhj3pWBuic+XhXzLieuolh/Ab7bzDaRXrjrU01V/Oo03C1qMSJhnub21Gpe5yfWgA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=C6hKg+fv; 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="C6hKg+fv" Received: by smtp.kernel.org (Postfix) with ESMTPSA id CAEF41F000E9; Mon, 10 Aug 2026 12:11:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1786363872; bh=1cleROhLoj+tECZ77BVaS91/gkOPGCBSYBgJhOj5vyg=; h=From:To:Cc:Subject:Date:Reply-To; b=C6hKg+fvJQwKJS5TOtGL4rQkimsb/e4PTbQDk1+WJ3YIU3UzdrSAPHMvgfx+d8L0d WR8Yjtnsoskp7ZYjNRmg2ftNZPBCOoLUAMpOPfHqC2aFvXZZsb5pvx07C5Nn+8bsf/ ImKqBTHZC4MmG7b+JkAzpd6TB95bP7iVr8F+sUWA= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-68339: Bluetooth: btusb: validate Realtek vendor event length Date: Mon, 10 Aug 2026 14:00:56 +0200 Message-ID: <2026081037-CVE-2026-68339-a754@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=3065; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=xj4OcCwvxP6xQzB6klQa5diEM4sEWtBlMJY6cQtP/Is=; b=owGbwMvMwCRo6H6F97bub03G02pJDFmVeza+rVhw5YD0kcU3vq69wfFL5hf/8crgtrshTbt7y kNLmqZ7dMSyMAgyMciKKbJ82cZzdH/FIUUvQ9vTMHNYmUCGMHBxCsBEvLwYFsyckp5vkCHKp7ZO ftq0moe56W75Qgzzc5ebGgXr7VaTPDr584zPMQc1jc0XAAA= 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: btusb: validate Realtek vendor event length btusb_recv_event_realtek() reads the event code at data[0] and the Realtek subevent code at data[2] before deciding whether to consume a vendor event as a coredump. For example, the two-byte event ff 00 contains a complete vendor-event header declaring zero parameters. The old classifier still reads a nonexistent third byte and can misclassify the event as a coredump if the adjacent byte is 0x34. Require the HCI event header and first parameter to be present before inspecting the Realtek subevent code. Short events continue through the normal HCI receive path, which owns their protocol validation. The Linux kernel CVE team has assigned CVE-2026-68339 to this issue. Affected and fixed versions =========================== Issue introduced in 6.6 with commit 044014ce85a17c0b7fab8e5df0925792010c29b2 and fixed in 6.6.148 with commit 8de58bfa26e028f99271dde5a92107cd07f5e063 Issue introduced in 6.6 with commit 044014ce85a17c0b7fab8e5df0925792010c29b2 and fixed in 6.12.101 with commit 400267bab0f4076088e163e58cad2bb41c3cf5e7 Issue introduced in 6.6 with commit 044014ce85a17c0b7fab8e5df0925792010c29b2 and fixed in 6.18.42 with commit 8881daaafadbe7fb2b7341d16a3949114409c90c Issue introduced in 6.6 with commit 044014ce85a17c0b7fab8e5df0925792010c29b2 and fixed in 7.1.6 with commit 24b0758193d70da47ef8b979153d2a181dbdf34e Issue introduced in 6.6 with commit 044014ce85a17c0b7fab8e5df0925792010c29b2 and fixed in 7.2-rc5 with commit df541cd485ff80a5ddc579d99687bc7506df9851 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-68339 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: drivers/bluetooth/btusb.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/8de58bfa26e028f99271dde5a92107cd07f5e063 https://git.kernel.org/stable/c/400267bab0f4076088e163e58cad2bb41c3cf5e7 https://git.kernel.org/stable/c/8881daaafadbe7fb2b7341d16a3949114409c90c https://git.kernel.org/stable/c/24b0758193d70da47ef8b979153d2a181dbdf34e https://git.kernel.org/stable/c/df541cd485ff80a5ddc579d99687bc7506df9851