CVE-2026-99316: ALSA: usx2y: Initialize idle URBs before submitting streams
In the Linux kernel, the following vulnerability has been resolved:
ALSA: usx2y: Initialize idle URBs before submitting streams
usbstreamstart() submits the first two capture and playback URBs and only afterwards assigns sk->idleinurb, sk->idleouturb, sk->completedinurb and sk->completedouturb to the remaining two URBs of each direction.
A transfer can complete as soon as usbsubmiturb() has been called, so the completion handler icapturestart() or iplaybackstart() may run before those pointers are set. While the stream is still being synchronized (state below usbstreamsync1), streamstart() then calls playbackprepfreqn(sk, sk->idleouturb) with sk->idleouturb 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:playbackprepfreqn+0x11c/0x4a0 sound/usb/usx2y/usbstream.c:33 Call Trace: <IRQ> streamstart+0x5dc/0x8d0 sound/usb/usx2y/usbstream.c:596 icapturestart+0x3da/0x710 sound/usb/usx2y/usbstream.c:654 usbhcdgivebackurb+0x238/0x550 drivers/usb/core/hcd.c:1657 usbgivebackurbbh+0x20b/0x530 drivers/usb/core/hcd.c:1691 tasklethiaction+0xa/0x20 kernel/softirq.c:994 handlesoftirqs+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
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Compensating control
Initialize and assign the idle URB pointers before submitting the capture and playback streams, so completion handlers cannot use them while they are NULL.
Event History
Frequently Asked Questions
Which systems are exposed to this issue?
Systems using the Linux kernel with the ALSA usx2y USB audio streaming path are exposed when capture or playback streams are started. The failure occurs in the usx2y driver’s USB URB submission and completion handling.
What must happen for the fault to be triggered?
A submitted capture or playback USB request must complete before the driver initializes its idle and completed URB pointers. During stream synchronization, the completion path can then use an uninitialized NULL idle output URB and dereference it.
What is the observable impact?
The described outcome is a kernel NULL-pointer dereference, producing an Oops/general protection fault in playback_prep_freqn(). This can disrupt the affected audio stream and crash the kernel.