In the Linux kernel, the following vulnerability has been resolved: ALSA: hwdep: Serialize DSP load requests The check of the loaded DSP indices and the call of the driver's dsp_load callback in snd_hwdep_dsp_load() are not serialized. A hwdep file descriptor can be shared among threads, or inherited across fork, so two SNDRV_HWDEP_IOCTL_DSP_LOAD requests for the same index can both observe the index as unloaded and enter the driver's callback concurrently, even though the device itself is opened exclusively. This breaks the assumption behind hw->dsp_loaded that a firmware index is loaded only once. For example, snd-usb-usx2y hits WARN_ON(usx2y->as04.buffer) in usx2y_async_seq04_init() and may allocate the US-428 sequence URBs twice. Serialize the check, the callback invocation and the bookkeeping with a per-hwdep mutex, so that the second request returns -EBUSY.
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-99317 is a race condition vulnerability in the Linux kernel's ALSA (Advanced Linux Sound Architecture) hwdep subsystem that allows concurrent DSP (Digital Signal Processor) load requests to bypass serialization checks. The vulnerability exists because the validation of loaded DSP indices and the subsequent driver callback invocation lack proper synchronization mechanisms. When a hwdep file descriptor is shared between threads or inherited across process forks, multiple threads can simultaneously observe an unloaded DSP index and trigger the driver's dsp_load callback concurrently, leading to potential device state corruption, privilege escalation, or denial of service. This affects any Linux system running vulnerable kernel versions that use ALSA sound card DSP functionality, particularly systems with shared audio device access or containerized environments where multiple processes interact with the same audio hardware.
While Casky currently shows zero matching skills for this specific CVE, practitioners using Casky's platform would typically identify this vulnerability pattern through techniques mapped to Improper Synchronization (CWE-662 family) and Resource Competition (T1491-adjacent patterns in concurrent execution contexts). A detection approach would focus on identifying unserialized state checks followed by privileged operations—analyzing kernel driver interactions for TOCTOU (Time-of-Check-Time-of-Use) patterns, particularly in ioctl handlers. Security practitioners reviewing kernel audit logs and driver behavior would look for indicators of concurrent callback invocations targeting the same resource index, abnormal DSP state transitions, or repeated device initialization attempts from multiple execution contexts. As Casky's skill mapping expands to cover kernel-level concurrency vulnerabilities and synchronization defects, practitioners will gain enhanced visibility into these hardware-interface attack surfaces.
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-99317. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation