CVE-2026-99316
ALSA: usx2y: Initialize idle URBs before submitting streams
What happened?
In the Linux kernel, the following vulnerability has been resolved:
ALSA: usx2y: Initialize idle URBs before submitting streams
usb_stream_start() submits the first two capture and playback URBs and only afterwards assigns sk->idle_inurb, sk->idle_outurb, sk->completed_inurb and sk->completed_outurb to the remaining two URBs of each direction.
A transfer can complete as soon as usb_submit_urb() has been called, so the completion handler i_capture_start() or i_playback_start() may run before those pointers are set. While the stream is still being synchronized (state below usb_stream_sync1), stream_start() then calls playback_prep_freqn(sk, sk->idle_outurb) with sk->idle_outurb still NULL, and the packet descriptors are written through that NULL pointer:
Oops: general protection fault, probably for non-canonical address 0xdffffc0000000018: 0000 [#1] SMP KASAN KASAN: null-ptr-deref in range [0x00000000000000c0-0x00000000000000c7] RIP: 0010:playback_prep_freqn+0x11c/0x4a0 sound/usb/usx2y/usb_stream.c:33 Call Trace: <IRQ> stream_start+0x5dc/0x8d0 sound/usb/usx2y/usb_stream.c:596 i_capture_start+0x3da/0x710 sound/usb/usx2y/usb_stream.c:654 __usb_hcd_giveback_urb+0x238/0x550 drivers/usb/core/hcd.c:1657 usb_giveback_urb_bh+0x20b/0x530 drivers/usb/core/hcd.c:1691 tasklet_hi_action+0xa/0x20 kernel/softirq.c:994 handle_softirqs+0x16f/0x440 kernel/softirq.c:645 </IRQ>
The four URBs referenced by these pointers are allocated long before and do not depend on any transfer state, so assign them before the submit loop. Keeping the assignment inside the retry path also restores a well-defined URB rotation when the start frame mismatch handling kills and resubmits the streams.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: 030a07e441296c372f946cd4065b5d831d8dc40c to < cc826d8f6074305af7bf1d2b7c13564d194db914; affected: 030a07e441296c372f946cd4065b5d831d8dc40c to < 1f32f490350fae3d64f60b5ab9b02e5254fa0a90; affected: 030a07e441296c372f946cd4065b5d831d8dc40c to < aa91b5324b5c856e18a9d356df875b29fbedd33a; affected: 030a07e441296c372f946cd4065b5d831d8dc40c to < ceb0d8c22473933099b46cec70639d0f1f7c68ad | See vendor advisory |
| LinuxLinux | affected: 2.6.28; unaffected: 0 to < 2.6.28; unaffected: 6.12.118 to ≤ 6.12.*; unaffected: 6.18.64 to ≤ 6.18.*; unaffected: 7.3.5 to ≤ 7.3.*; unaffected: 7.4-rc2 to ≤ * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-99316
- https://git.kernel.org/stable/c/cc826d8f6074305af7bf1d2b7c13564d194db914
- https://git.kernel.org/stable/c/1f32f490350fae3d64f60b5ab9b02e5254fa0a90
- https://git.kernel.org/stable/c/aa91b5324b5c856e18a9d356df875b29fbedd33a
- https://git.kernel.org/stable/c/ceb0d8c22473933099b46cec70639d0f1f7c68ad