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 EA6E74EBACC for ; Fri, 4 Sep 2026 15:19:08 +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=1788535150; cv=none; b=OX3x6UCqYY57rPsM7jW7slciW89b7agFZU5sPnpi8dJD3igSdElXZBGvhahXxqG4Vehcf/sOApQmuOM/QzhWjPS50TqeqZSxcFr2Qh3Ak1vaKnSsjfBdBJ0LssahuxMOnHAfmQnUL7nYuvZXYiFN4xjVjZZGepIS3eCsvysQNGU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1788535150; c=relaxed/simple; bh=T1PitWq3yWrtUTjT8mtNL4EvBM2gRVdU971ogs3qc5A=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=snTbOt0cf8J3ks8kYEmqjxsfns6qN/ffIcdDOrR01Mr3TgY4AWcxIa11csfe8RMWDXgoOOXpyn5+hM+GupyonATbUmg1hRFhWRyhoEvWB08pvYirz+cn0y9a+IIENM2Qw/D8hK4XJ6ki5TGfz8vc08q2YrCFNvfhaeF1N8eEDGc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=vmCwA5si; 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="vmCwA5si" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5F9411F00A3D; Fri, 4 Sep 2026 15:18:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1788535148; bh=ewF2jUh2XAOENTxKJZCHnNvUZNKcc70mdQghFA4+2vA=; h=From:To:Cc:Subject:Date:Reply-To; b=vmCwA5siDU7n2Aqzc2EBiwERKj0YijFkrQoOQ9Ng1cd3C1zJ5L4r7Qty1KpcwYLj/ s6dvsbMfBI3kXNhMCqIJdGIEbcdpJTgzCRuPQTWkJ/prq7O+cCU9yQhOZK9tK9bCYe cUqFI/KuaDi9k5nLvMIv7452/ENjDU+czKLadizU= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-80815: ALSA: scarlett2: Use a private URB for the notification endpoint Date: Fri, 4 Sep 2026 17:11:54 +0200 Message-ID: <2026090412-CVE-2026-80815-4fd4@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=3923; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=exDx7YAek1sh0QHw+dezKJFR4ep1z81IqoAR5bDFKxs=; b=owGbwMvMwCRo6H6F97bub03G02pJDFmz7k/wbzI/ptD49bh88KWPR/5eOeGuqJMRWDsx68wB4 /RvEwVnd8SyMAgyMciKKbJ82cZzdH/FIUUvQ9vTMHNYmUCGMHBxCsBEHP4xzNMwbbh1Zn7rHk51 Jc6zPy44d8gGeTDM4ZFis4n66GzC+26bwfd4j/QFLfGVAA== 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: scarlett2: Use a private URB for the notification endpoint scarlett2_init_notify() used mixer->urb, which snd_usb_mixer_status_create() allocates for the UAC2 status interrupt endpoint and mixer.c manages. On a device with that endpoint, the "already in use" check fires on the status URB and returns 0 for success without doing anything. No notification URB is submitted, and cmd_done is left zeroed because it is initialised past that check and nowhere else. scarlett2_usb_init() then issues SCARLETT2_USB_INIT_1 and wait_for_completion_timeout() would crash adding to the zeroed wait.head. Use a separate URB in scarlett2_data, as done for FCP, and initialise cmd_done in scarlett2_init_private(). mixer.c was also freeing the URB in snd_usb_mixer_free() and resubmitting it in snd_usb_mixer_activate(), so scarlett2 must now do both: add scarlett2_cleanup_urb(), called from private_free and private_suspend, and a private_resume callback to re-establish the URB after resume. scarlett2_init_notify() is reached from there, and the URB kill path in scarlett2_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. Also free the URB if the transfer buffer allocation fails, and both if usb_submit_urb() fails. Move scarlett2_init_notify() up next to scarlett2_cleanup_urb() so scarlett2_init_private() can reference it without a forward declaration. The Linux kernel CVE team has assigned CVE-2026-80815 to this issue. Affected and fixed versions =========================== Issue introduced in 6.10 with commit 1b65088958cadab04d5d34a8615e2466b1b48ecb and fixed in 6.12.106 with commit 013448eb7b0d0b91d6168685dab10e9b41baa825 Issue introduced in 6.10 with commit 1b65088958cadab04d5d34a8615e2466b1b48ecb and fixed in 6.18.47 with commit 4305e4b52acc0ca67dcfdf8f73dd943dab508ae8 Issue introduced in 6.10 with commit 1b65088958cadab04d5d34a8615e2466b1b48ecb and fixed in 7.1.11 with commit 04df0232a6976845cd9c9e83b6c26215759be667 Issue introduced in 6.10 with commit 1b65088958cadab04d5d34a8615e2466b1b48ecb and fixed in 7.2.1 with commit ecd2f83a4ddc078901e7104144cb6c5e5db3b7cf Issue introduced in 6.10 with commit 1b65088958cadab04d5d34a8615e2466b1b48ecb and fixed in 7.3-rc1 with commit cd17d6ff7b7d2b1dd9bcc80ae7b4a83773f918c6 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-80815 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/mixer.c sound/usb/mixer.h sound/usb/mixer_scarlett2.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/013448eb7b0d0b91d6168685dab10e9b41baa825 https://git.kernel.org/stable/c/4305e4b52acc0ca67dcfdf8f73dd943dab508ae8 https://git.kernel.org/stable/c/04df0232a6976845cd9c9e83b6c26215759be667 https://git.kernel.org/stable/c/ecd2f83a4ddc078901e7104144cb6c5e5db3b7cf https://git.kernel.org/stable/c/cd17d6ff7b7d2b1dd9bcc80ae7b4a83773f918c6