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 soun
Casky was already ahead
This CVE exploits attack patterns that Casky's 0matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.
CVE-2026-99316 is a race condition vulnerability in the Linux kernel's ALSA USB audio driver (usx2y module) where idle USB Request Blocks (URBs) are not properly initialized before stream submission begins. When usb_submit_urb() is called to submit the initial capture and playback URBs, the completion handlers can execute immediately, but the idle URB pointers (sk->idle_inurb, sk->idle_outurb, sk->completed_inurb, sk->completed_outurb) have not yet been assigned. This creates a window where URB completion handlers access uninitialized memory, potentially leading to kernel memory corruption, information disclosure, or denial of service. Linux systems with USB audio devices (particularly Tascam US-X2Y interfaces) that actively use audio streaming are vulnerable.
While this CVE lacks direct MITRE ATT&CK technique mapping, Casky's AI-driven analysis would identify this as a Memory Corruption (CWE-119 adjacent) vulnerability that facilitates Privilege Escalation (T1134) or Persistent Access patterns through kernel exploitation. A practitioner using Casky would see detection signals around: (1) abnormal kernel module initialization sequences where resource handles are accessed before allocation, (2) USB subsystem state inconsistencies in kernel audit logs, and (3) unexpected memory access patterns in audio driver traces. The platform's 754 mapped security skills would correlate this with kernel hardening assessment skills and driver verification techniques, alerting practitioners to audit USB audio driver initialization code and apply kernel patches as mitigation.
Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →
Casky has 0 skills that investigate the attack patterns behind CVE-2026-99316. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation