Quick answers
- Is CVE-2026-93808 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93808 being exploited in the wild.
- How severe is CVE-2026-93808?
- Informational severity, published 24 September 2026.
- Which products and versions are affected?
- Unknown Linux kernel all versions prior to fix commit aba30af07d4fe499b50209801eba9da8a815522f.
- Is there a fix for CVE-2026-93808?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-93808 attacked?
- It is attacked from the adjacent network, in an operating system.
- Am I affected by CVE-2026-93808?
- Check whether you run Unknown Linux kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The usb_ep1_command_reply_dispatch() function in sound/usb/caiaq/device.c and snd_caiaq_input_read_analog() in sound/usb/caiaq/input.c access fixed offsets in USB URB buffers without first checking that urb->actual_length contains sufficient bytes. This allows reads of uninitialized kernel memory when a USB device returns truncated responses. The fix adds per-command payload length validation before accessing buffer fields.
Affected products
- <UNKNOWN> Linux kernel all versions prior to fix commit aba30af07d4fe499b50209801eba9da8a815522f
Timeline
- 2026-09-24: disclosed