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=1795154051; b=FRbeMiEMsv1Hha2ZdQWRxKeihbsmeujK5PbuAB+Vgeeig5S589SiTq+5bL2v3Jtmy0Jw SD8lCWJ+xdRWi498qiwo5wnJB2F+I656I53mJ8QgAniDwhXXreGBkpIHU3+aQwUa8aYy2 p03vlpjLETqCamRBsWnsGrY/s46Q5zce6jeziyzq/QgvINIZ97Wcut+Os0INeWW5EsFcJ 79A+c14p+NCBy/8bRzYiyzlztWHd1ubT1S7QD2R4xGQPUvRjFCUn7Kxzzl2wOTgfz87MO rFCElTmP3MEyqoLOtixAPkENrbSP0b1tqkQTk/1bmk59CqNNHGLCpwYMl+WYCwltUug== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154051; 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=a/ZV1Wa8BiuePsFBQiQ0nuqCyDdP+XBLi27t62dqu8o=; b=e29XxXxYcY1sOqjauyVdLBXFc+UY8yIdQ5uqFik30qDMQ0NTJFizUFPR6c8AaeeGsrOp bnJTTNwYJ1p0D1r9v/f1NpfDp9ZpeWzvStKbv74Fl6CMrXe5BjdDV/RGGw2Y6kaTQJdHk G/FX6XzzjMSndHzWDRffQsTZF4UXalWUGHqaDLQbadBZhSGEPWMxflrOzcrbbBIaZEGN1 +eHMOGCXqpbDgQwi13cOChdk+jZ4TTW773arPTHqU3rUDGFUi8cRON1u+FebmEF5vodEu I6qjPTGzx5rSskurKsKUYA7/xxua1KfVvrBhAGNYFUbxd5suEYdCXfr7GwhMPb2ub3w== 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=ZttRvdtV; 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 0AEEE606A320 for ; Fri, 20 Nov 2026 05:54:11 +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=ZttRvdtV Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5858B1F000C4; Fri, 20 Nov 2026 05:54:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154050; bh=a/ZV1Wa8BiuePsFBQiQ0nuqCyDdP+XBLi27t62dqu8o=; h=From:To:Cc:Subject:Date:Reply-To; b=ZttRvdtV67IkqZ8temI33vuv3H49FST2TOQhZYDgAL1Ikjno122l8odVSrndpsdDe oY+Rt8jpbYzYxwalVHouVSTgyhmr4F5vbEUAq2p0T6XESQ1ztx3cDPvTQT7MQwAhXC fUgAsXVXvXHmBJTTZoYfSYSGgRZcE+kRvc6BnnvA= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99609: ALSA: usx2y: Require a buffer of two URBs Date: Fri, 20 Nov 2026 06:49:55 +0100 Message-ID: <2026112028-CVE-2026-99609-d896@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=4271; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=5bRDk1ZLgMmqiSs3PoHl4E8F/jVSVnWfdlEdejyyfDo=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/72ceThRUubXa23nRkta1Ey2TMhovNCzc+vQLI+/Mi sQvp/P+d8SyMAgyMciKKbJ82cZzdH/FIUUvQ9vTMHNYmUCGMHBxCsBE3JwZZjFvntH7POha0Y6r 9z8ei0lq+qrL/4NhfhhTu+DtB98zk5rsD7sKVBaeO/5sLwA= 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: Require a buffer of two URBs usx2y_urb_capt_retire() wraps the ring buffer once per packet and usx2y_urb_play_prepare() once per URB of nr_of_packs() packets of up to 50 frames. Both assume that the data fits in the buffer, and the hw constraints only require about two 1 ms periods, so a packet larger than the buffer on capture, or a URB larger than the buffer on playback, violates that assumption. Constrain SNDRV_PCM_HW_PARAM_BUFFER_SIZE in snd_usx2y_pcm_open() to at least two URBs, 2 * nr_of_packs() * 50 frames, for both directions. The bound is in frames and derived from the driver's own packet limit, so it does not read the endpoint, whose altsetting is only selected in prepare. Two URBs rather than one, because the position advances by a URB on playback and only moves when a URB is less than the whole buffer. Keep a guard in usx2y_urb_capt_retire() that drops a packet larger than the buffer, for the case the constraint makes unreachable. With nrpacks above about 163 (S16_LE) or 109 (S24_3LE) the bound exceeds the 64 KiB buffer the substream preallocates (twice that with the preallocation raised to its 128 KiB maximum), so hw_params fails for those module settings. That is intended: the driver cannot be safe with a URB larger than half the largest buffer. Reproduced on 7.3-rc7 with a USB/IP device presenting the US-122 interface layout and 1024-byte packets into a 512-byte capture buffer: BUG: KASAN: out-of-bounds in i_usx2y_urb_complete+0x1285/0x1ac0 Read of size 18446744073709551104 at addr ffff88800e448800 by task vhci_rx/83 Tested on 7.3-rc7 with the same device, S16_LE at 44100 Hz, nrpacks 4, so the bound is 400 frames. A 128-frame capture buffer and a 200-frame playback buffer are refused at hw_params with EINVAL. A 400-frame buffer streams for 30 s in each direction with the position advancing inside the buffer and no KASAN report; the capture guard did not fire. The same 400-frame capture buffer with S24_3LE, which selects altsetting 2 in prepare, streams for 30 s with the same result. The Linux kernel CVE team has assigned CVE-2026-99609 to this issue. Affected and fixed versions =========================== Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 6.12.118 with commit 44c6971a79efdb46cd5c9f492f0ad65aafe05add Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 6.18.64 with commit 5356d89f5e581dc207c7a607fe585d3e1cb2471c Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 7.3.5 with commit 824fdf771cb7cbe9ae50eaec588eaf1acee6da94 Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 7.4-rc2 with commit 4cbb826b3b36df6c275454287ba1df4564a5370b 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-99609 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/44c6971a79efdb46cd5c9f492f0ad65aafe05add https://git.kernel.org/stable/c/5356d89f5e581dc207c7a607fe585d3e1cb2471c https://git.kernel.org/stable/c/824fdf771cb7cbe9ae50eaec588eaf1acee6da94 https://git.kernel.org/stable/c/4cbb826b3b36df6c275454287ba1df4564a5370b