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 0BB8D4EBACC for ; Fri, 4 Sep 2026 15:19:23 +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=1788535164; cv=none; b=D6QUpCHUqVSaP+8EBukTvOflw8g82YLDm/Y5rIfc4AstxSWV00CZpy3iwLYEZLUY/w9IKBMoRLwM39ZpyCjGksJ/dy2qTQ1bi52nHNmlHPiIX8T1XsXSbpRfGsRzT/MYwmPbb6dAASeXX5BwGFzqmMlbQdJwySjSxOIk1AZyjwA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1788535164; c=relaxed/simple; bh=EYwiDeqbfqKD0V2RO1BwKu2Vh530khE6RUlnUFI8xBM=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=AuD0lEPyh+fLznkUuvO0R3F+lVYodONBQYIgcw5+jRmWG4YzcgvrH6JLvrn05H7rq3sVpozZNCDAj9gkFaHrLr+223gPXQAefRcI718SduUlacCbDLRfotziMZ2RuUGpQIU5RANXquEUmNKwc9LFolGvZAl1lZrG4LRIinMviJ4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=JqAF6oS0; 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="JqAF6oS0" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 1E8641F00A3D; Fri, 4 Sep 2026 15:19:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1788535162; bh=4KYAy+9kyloNhnwV73IYp9hcDnu93vskWpEKeKF8rok=; h=From:To:Cc:Subject:Date:Reply-To; b=JqAF6oS09e+Kegao6CaQoIu8lWQ/BubHcDYJ3gu2p7ylKY+QDSpIVfxJ0QLWUzinG hlOZVfCw33kr9qdbLu7AyreeaBvVrHwxLT2NAtjvoIeTE3m5AVtLcJ+S43wrUypsIy wqR2y4twya8sEya6noAZoex6xQfVRkzK5Xpb7Vk4= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-80816: ALSA: FCP: Use a private URB for the notification endpoint Date: Fri, 4 Sep 2026 17:11:55 +0200 Message-ID: <2026090412-CVE-2026-80816-eeb9@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=3221; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=GEaERYDDNlu3R0twfshLDhxqLk0UtNxqIKlwoudsSQI=; b=owGbwMvMwCRo6H6F97bub03G02pJDFmz7k8ovTxTiaNCtq8wq92TNVCWq/7uCsOlC9cVpM3i2 8b04V5yRywLgyATg6yYIsuXbTxH91ccUvQytD0NM4eVCWQIAxenAEzkdwXDghPqqgzJLzedYUm1 ZK3ZMq1jXn+9OMP8iD8JDjF9D+bknmSRlagUajbbtGgpAA== 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: ALSA: FCP: Use a private URB for the notification endpoint fcp_init_notify() used mixer->urb, which snd_usb_mixer_status_create() allocates for the optional UAC2 status interrupt endpoint and mixer.c kills, resubmits and frees. On a device with that endpoint, fcp_init_notify()'s "already set up" early return fires on the status URB and returns success without doing anything. No FCP notification URB is submitted, and cmd_done is left zeroed because it is initialised past that early return and nowhere else. fcp_init() then issues init1_opcode and wait_for_completion_timeout() would crash adding to the zeroed wait.head. fcp_cleanup_urb() would also kill and free mixer.c's status URB. Use a separate URB in fcp_data, and initialise cmd_done in fcp_init_private() where fcp_data is allocated. fcp_init_notify() is reached again after suspend via fcp_reinit(), and the URB kill path in fcp_notify() completes cmd_done, leaving a stale count that would satisfy the next command's wait before the device ACKs. Use reinit_completion() to clear it. The Linux kernel CVE team has assigned CVE-2026-80816 to this issue. Affected and fixed versions =========================== Issue introduced in 6.14 with commit 46757a3e7d50dac923888e7fbe68377736f13c70 and fixed in 6.18.47 with commit 65aceb45ca91ddb7f7ed178821f481b34da35543 Issue introduced in 6.14 with commit 46757a3e7d50dac923888e7fbe68377736f13c70 and fixed in 7.1.11 with commit 5da21a434171e8ecf1d992c6f1d84c0c706fd395 Issue introduced in 6.14 with commit 46757a3e7d50dac923888e7fbe68377736f13c70 and fixed in 7.2.1 with commit 6db3c1d7e2872c9904e05ca8e0515920776a3c9c Issue introduced in 6.14 with commit 46757a3e7d50dac923888e7fbe68377736f13c70 and fixed in 7.3-rc1 with commit 918b8d231c571c50a00efe92ffc8404a537a0490 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-80816 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: sound/usb/fcp.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/65aceb45ca91ddb7f7ed178821f481b34da35543 https://git.kernel.org/stable/c/5da21a434171e8ecf1d992c6f1d84c0c706fd395 https://git.kernel.org/stable/c/6db3c1d7e2872c9904e05ca8e0515920776a3c9c https://git.kernel.org/stable/c/918b8d231c571c50a00efe92ffc8404a537a0490