In the Linux kernel, the following vulnerability has been resolved: USB: serial: digi_acceleport: fix write buffer corruption The digi_write_inb_command() is supposed to wait for the write urb to become available or return an error, but instead it updates the transfer buffer and tries to resubmit the urb on timeout. To make things worse, for commands like break control where no timeout is used, the driver would corrupt the urb immediately due to a broken jiffies comparison (on 32-bit machines this takes five minutes of uptime to trigger due to INITIAL_JIFFIES). Fix this by adding the missing return on timeout and waiting indefinitely when no timeout has been specified as intended. This issue was (sort of) flagged by Sashiko when reviewing an unrelated change to the driver.
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-64333 is a critical buffer corruption vulnerability in the Linux kernel's digi_acceleport USB serial driver. The flaw exists in the digi_write_inb_command() function, which fails to properly synchronize access to write URBs (USB Request Blocks). Instead of correctly waiting for buffer availability or returning an error on timeout, the function overwrites active transfer buffers and attempts URB resubmission, leading to memory corruption. This vulnerability affects any system using Digi AccelePort USB serial devices, including industrial control systems, medical devices, and embedded Linux deployments that rely on this driver for serial communication.
While CVE-2026-64333 lacks mapped MITRE ATT&CK techniques and CWE classification, Casky's Claude-powered analysis would identify this as a memory safety issue enabling potential code execution through techniques like T1190 (Exploit Public-Facing Application) or T1203 (Exploitation for Client Execution). Practitioners using Casky would detect anomalies in kernel memory writes, unexpected USB driver behavior, and potential privilege escalation attempts stemming from buffer overflow exploitation. The vulnerability's presence—particularly on 32-bit systems with broken jiffies comparison logic—represents a kernel-level attack surface requiring immediate patching, with detection focused on monitoring USB device driver interactions and kernel panic signatures.
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-64333. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation