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 E0F73313E05 for ; Tue, 13 Jan 2026 15:36:40 +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=1768318601; cv=none; b=M5RiMOucLWgQ8sbUymUaZOCKIVCYl1CC7Z0ldv2/0ZFzyRWZppC4ujTr4nQXVepGRyzLBhdJqi2bMHKpDjdsoxQMKmgqD2m+2gmjF6Rd/EtLFF5/7aO8QAs/TBI21Hfecoii4tCWDmCJfB0EhTvDrZTQZ5eMhbK0vvvwvL3aMyY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768318601; c=relaxed/simple; bh=tQARRpJSUkKcX+QB9o3umRiKZdXl9YKKE04+wlbT6co=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=iipWWneGGrwbDVdJU248NA7fcfRRQOsnk9lfVcYZeLWVrvMoacdbGCOQ7gXRqGu3CiE0jGtOzNjBmY/lbSy7WvK/eIqpJI4iC6XcFtu1tp/SDuxxScMud7xGJDR4APcPrH81Fjjc/KHra4AZvUBSI374NdVLnNcGuCUVfQETUEc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=Q7+KbF/t; 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="Q7+KbF/t" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6FFF2C116C6; Tue, 13 Jan 2026 15:36:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1768318600; bh=tQARRpJSUkKcX+QB9o3umRiKZdXl9YKKE04+wlbT6co=; h=From:To:Cc:Subject:Date:Reply-To:From; b=Q7+KbF/tLmGYYEYJ3+ykJb4ySQC4V9WBZ67SJ0IUGv1lCyIGRm7mKfwb1VhtOMP6U ai9nIXbMVPqm8RrPdSKUJxslzpzpxJdB86T0B9d8YuytbiYa95xSoHi9Dbia7BVsnL yGrXVMmPCtWxPuiJqyD9kI+g27zVpIbRZU2Ywo34= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2025-71082: Bluetooth: btusb: revert use of devm_kzalloc in btusb Date: Tue, 13 Jan 2026 16:35:41 +0100 Message-ID: <2026011339-CVE-2025-71082-ef8a@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=3123; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=POskUQkn1vmk1cvr5QRtFmWyXiCcTmKBlKZECPeLxR4=; b=owGbwMvMwCRo6H6F97bub03G02pJDJlpad4rv7RdFjk8Zd2zg95Lz3mm7X1p8el1nWF45qWJY f/S1sov6YhlYRBkYpAVU2T5so3n6P6KQ4pehranYeawMoEMYeDiFICJ7NnCsOBy9qH+7h1SJrO6 +6PkT13ymjBJYD7DglOTK7YeuHK1e8WHlICnTxoCft97MRMA 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: revert use of devm_kzalloc in btusb This reverts commit 98921dbd00c4e ("Bluetooth: Use devm_kzalloc in btusb.c file"). In btusb_probe(), we use devm_kzalloc() to allocate the btusb data. This ties the lifetime of all the btusb data to the binding of a driver to one interface, INTF. In a driver that binds to other interfaces, ISOC and DIAG, this is an accident waiting to happen. The issue is revealed in btusb_disconnect(), where calling usb_driver_release_interface(&btusb_driver, data->intf) will have devm free the data that is also being used by the other interfaces of the driver that may not be released yet. To fix this, revert the use of devm and go back to freeing memory explicitly. The Linux kernel CVE team has assigned CVE-2025-71082 to this issue. Affected and fixed versions =========================== Issue introduced in 3.7 with commit 98921dbd00c4e2e4bdd56423cb5edf98d57b45f7 and fixed in 6.1.160 with commit cca0e9206e3bcc63cd3e72193e60149165d493cc Issue introduced in 3.7 with commit 98921dbd00c4e2e4bdd56423cb5edf98d57b45f7 and fixed in 6.6.120 with commit c0ecb3e4451fe94f4315e6d09c4046dfbc42090b Issue introduced in 3.7 with commit 98921dbd00c4e2e4bdd56423cb5edf98d57b45f7 and fixed in 6.12.64 with commit 1e54c19eaf84ba652c4e376571093e58e144b339 Issue introduced in 3.7 with commit 98921dbd00c4e2e4bdd56423cb5edf98d57b45f7 and fixed in 6.18.4 with commit fdf7c640fb8a44a59b0671143d8c2f738bc48003 Issue introduced in 3.7 with commit 98921dbd00c4e2e4bdd56423cb5edf98d57b45f7 and fixed in 6.19-rc4 with commit 252714f1e8bdd542025b16321c790458014d6880 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-71082 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/cca0e9206e3bcc63cd3e72193e60149165d493cc https://git.kernel.org/stable/c/c0ecb3e4451fe94f4315e6d09c4046dfbc42090b https://git.kernel.org/stable/c/1e54c19eaf84ba652c4e376571093e58e144b339 https://git.kernel.org/stable/c/fdf7c640fb8a44a59b0671143d8c2f738bc48003 https://git.kernel.org/stable/c/252714f1e8bdd542025b16321c790458014d6880