From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795154048; b=LB0uYeQn6uzd+RHd0W2RFDdKLhi/ORSYmd/EsWti+gKXSHakx6nBFU/49REozsLt3MsJ 6V3RnkuhqsneH2PE6V3Ts4us3HQtU3ZsK13zW57NfOSJsZce/yeSmTJkO5UXmK/gt/tr7 fjqCdH8Cd8fAC4+H1b7ZaFVTLAuGlyJ0rMDSfSuODPRBqgI+dHdDZfME78eGzA4LVRASV zoXHbMxyKH+H3BEhWNM9tx2to3DRdK46GefxhZ50E+qrfu0hlrq6Ak7N0sNDmA3bCYT1J In7bzPRqWjOgcQ2Ya3EhhxhuGQozWnpeHwnENyC2g4XBVmjh2jY2eX5VtNBD1Hu1mGw== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154048; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: Reply-To:MIME-Version:Lines:X-Developer-Signature:X-Developer-Key: Content-Transfer-Encoding; bh=e1YbWjK9ZXLS6hWZLeCmvw0qKO73TzKcE3dQxK5u65U=; b=LUIu0HRZloiVz9dwSa606IzU7W6okWdymccekCx0MLvMnE0mM/htzGykVbpkrR4zB1VZ xPhk91bikdM0EbN4ugdfb88ROOC4Nwhceql6wn1sPwgxbZGJletRcnk2n86UQ5Y+mTLb4 dz4u5ICBJnrB7UbUHw8kG2VUxcbtmfMXgkk2IZkzcgYKtl+LY5rzI0pfJAkXDHBvxRDYb HubUF9HhzhrQCYWiVUszcr6ydWnoowTHyo7Bb7NRdpuqHqkySFn6j2oASd+NEqCMNmkOF 8DhdDFK8RT/CfhIcZ78WWGDMM1+wS7kVqEnCvaX9OAcUkmhd4VAiTYRvz8i7JRvkxwg== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=zg4SQiXm; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 183C0606A320 for ; Fri, 20 Nov 2026 05:54:08 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=zg4SQiXm Received: by smtp.kernel.org (Postfix) with ESMTPSA id 670621F000C6; Fri, 20 Nov 2026 05:54:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154047; bh=e1YbWjK9ZXLS6hWZLeCmvw0qKO73TzKcE3dQxK5u65U=; h=From:To:Cc:Subject:Date:Reply-To; b=zg4SQiXmK/Q55dQyQb/3z1GpFe57/K6RfbJxhg+h/Vcu3QTGg8kWyd1Kcg76pkFGL eCDaI/b4VCXi7aF1tOfqFfa/75EZmHzwuzbNfHGC6ZNB9J7dch3x1A8mZYTH0D+R6a y4/CN4j1TuyuyZaYl0B8KIAukkz4+3Mv3qX3c8Ks= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99608: ALSA: usx2y: Guard the playback copy Date: Fri, 20 Nov 2026 06:49:54 +0100 Message-ID: <2026112028-CVE-2026-99608-5dff@gregkh> X-Mailer: git-send-email 2.56.1 Reply-To: , X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=4635; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=+T6fiRKFG4fl0B1hYvO47JB+MIzqUyuBq75ZSXr2Sh8=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/72dcqWSQZfpx4+QUW/1Nj+e1xk+YfOOn5glGmxNOR 12epj7e2xHLwiDIxCArpsjyZRvP0f0VhxS9DG1Pw8xhZQIZwsDFKQAT+ZDOsGDaNp9us8JL+8Ru X9L9/+SDyZefvJ8ZFsx+cPPka7sJk/PtwrhdN/JlGgSeaQcA 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: usx2y: Guard the playback copy usx2y_urb_play_prepare() sums the packet lengths of a whole URB, copies that many frames with a single wrap, and sizes each playback packet from the capture packet's actual_length. Three things are unchecked: that the URB fits in the ring buffer, that a packet fits in the playback endpoint's maxpacksize, from which tmpbuf is allocated, and that actual_length is a whole number of frames. The ISO descriptors take the raw actual_length while transfer_buffer_length and the copies take count * stride, so a packet that is not a multiple of the stride makes the descriptors add up to more than the buffer, by up to stride - 1 bytes per packet. Return -EPIPE, as the existing packet-size check does, when the URB is larger than the buffer or a packet is larger than maxpacksize, and size each descriptor from whole frames, so the descriptors add up to transfer_buffer_length and each stays within maxpacksize. The buffer case is prevented by the previous patch and this is the guard for it; the other two depend only on the device. The first case is reachable on the unpatched driver with ordinary packets: on 7.3-rc7, a USB/IP device presenting the US-122 interface layout and sending 48-frame packets, with a 100-frame playback buffer (two 50-frame periods, inside the stock constraints), KASAN reports: BUG: KASAN: out-of-bounds in i_usx2y_urb_complete+0x79b/0x1ac0 Read of size 18446744073709551280 at addr ffff88800e6b02e0 by task vhci_rx/80 With both patches, the same device and a 200-frame playback buffer is refused at hw_params with EINVAL, and a 400-frame buffer plays for 30 s with the position advancing inside the buffer, no KASAN report and neither guard message. The maxpacksize check is not exercised: the emulated device reports the same wMaxPacketSize on both endpoints. The descriptor case is visible with capture packets of 195 bytes at stride 4 (48 frames and 3 bytes): without this change the four descriptors add up to 780 bytes for 768 bytes of data, and USB/IP's completion check refuses the URB ("total length of iso packets 780 not equal to actual length of buffer 768", -EPROTO), after which the driver stops the streams. With this patch every descriptor is 192 bytes, the descriptors add up to the data in every URB for 30 s, the position advances inside the buffer and KASAN reports nothing. The 48-frame playback run above is unchanged. The Linux kernel CVE team has assigned CVE-2026-99608 to this issue. Affected and fixed versions =========================== Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 6.12.118 with commit 116f158a6f6820a93faa12d46d5a2956cae4e4d2 Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 6.18.64 with commit 38bb5df007a80f81861a79228f7dae29e4e263c6 Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 7.3.5 with commit deeccc01999ed8982507945e5ca750e75f0437dc Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 7.4-rc2 with commit e2c6de52ffacb2c0f4076884ee3fdb744735a4cb 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-99608 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/usx2y/usbusx2yaudio.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/116f158a6f6820a93faa12d46d5a2956cae4e4d2 https://git.kernel.org/stable/c/38bb5df007a80f81861a79228f7dae29e4e263c6 https://git.kernel.org/stable/c/deeccc01999ed8982507945e5ca750e75f0437dc https://git.kernel.org/stable/c/e2c6de52ffacb2c0f4076884ee3fdb744735a4cb