CVE-2026-99609: Security vulnerability
In the Linux kernel, the following vulnerability has been resolved:
ALSA: usx2y: Require a buffer of two URBs
usx2yurbcaptretire() wraps the ring buffer once per packet and usx2yurbplayprepare() once per URB of nrofpacks() 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 SNDRVPCMHWPARAMBUFFERSIZE in sndusx2ypcmopen() to at least two URBs, 2 nrofpacks() 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 usx2yurbcaptretire() that drops a packet larger than the buffer, for the case the constraint makes unreachable.
With nrpacks above about 163 (S16LE) or 109 (S243LE) the bound exceeds the 64 KiB buffer the substream preallocates (twice that with the preallocation raised to its 128 KiB maximum), so hwparams 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 iusx2yurbcomplete+0x1285/0x1ac0 Read of size 18446744073709551104 at addr ffff88800e448800 by task vhcirx/83
Tested on 7.3-rc7 with the same device, S16LE 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 hwparams 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 S243LE, which selects altsetting 2 in prepare, streams for 30 s with the same result.
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.118 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.64 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5 - Compensating control
In snd_usx2y_pcm_open(), constrain SNDRV_PCM_HW_PARAM_BUFFER_SIZE to at least two URBs: 2 * nr_of_packs() * 50 frames, for both playback and capture.
- Compensating control
Keep a guard in usx2y_urb_capt_retire() that drops a capture packet larger than the buffer, including cases the buffer-size constraint is intended to make unreachable.
Frequently Asked Questions
Which systems are exposed to this issue?
Systems using the Linux kernel's ALSA usx2y driver are exposed when that driver handles capture or playback buffers that are smaller than the driver's packet or URB processing assumptions. The issue concerns both capture and playback directions.
What condition triggers the vulnerability?
The problem occurs when a capture packet is larger than the PCM buffer or when a playback URB, containing up to nr_of_packs() packets of up to 50 frames, is larger than the buffer. The prior hardware constraints could permit buffers of roughly two 1 ms periods, which may be insufficient.
What mitigation is available if the fix cannot be deployed immediately?
Use a PCM buffer size of at least two URBs: 2 multiplied by nr_of_packs() multiplied by 50 frames, for both capture and playback. The driver also retains a capture-side guard that drops packets larger than the buffer, although that case is intended to be unreachable with the corrected constraint.
How does the fix prevent the issue?
The fix constrains SNDRV_PCM_HW_PARAM_BUFFER_SIZE in snd_usx2y_pcm_open() to a minimum of two URBs. This accounts for playback position advancing by a full URB and for capture processing wrapping the ring buffer once per packet.