In the Linux kernel, the following vulnerability has been resolved: HID: logitech-hidpp: fix race condition when accessing stale stack pointer The driver uses hidpp->send_receive_buf to point to a stack-allocated buffer in the synchronous command path (__do_hidpp_send_message_sync). However, this pointer is not cleared when the function returns. If an event is processed (e.g. by a different thread) while the send_mutex is held by a new command, but before that command has updated send_receive_buf, the handler (hidpp_raw_hidpp_event) will observe that the mutex is locked and dereference the stale pointer. This results in an out-of-bounds access on a different thread's kernel stack (or a NULL pointer dereference on the very first command). Fix this by: 1. Clearing hidpp->send_receive_buf to NULL before releasing the mutex in the synchronous command path. 2. Moving the assignment of the local 'question' and 'answer' pointers inside the mutex_is_locked() block in the handler, an
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-99313 is a race condition vulnerability in the Linux kernel's Logitech HID++ driver that occurs when a stale stack pointer is accessed during asynchronous event processing. The vulnerability exists in the synchronous command path where hidpp->send_receive_buf points to a stack-allocated buffer, but this pointer is never cleared when the function returns. If an event is processed by a different thread while send_mutex is held, the driver may dereference a pointer to memory that has been reclaimed or overwritten on the stack, potentially leading to information disclosure, denial of service, or code execution. This affects Linux systems with Logitech HID devices, impacting both desktop users and server environments where such peripherals may be in use.
While Casky.ai currently shows zero matching skills for this specific CVE, practitioners using the platform would typically look for detection patterns aligned with memory corruption and race condition exploitation techniques. Classic MITRE ATT&CK techniques like Exploitation for Privilege Escalation (T1548) and Exploitation for Credential Access (T1555) would be relevant if weaponized. A security team leveraging Casky's Claude AI-powered analysis would focus on identifying kernel-level memory access anomalies, stack pointer validation failures, and thread synchronization gaps. By analyzing kernel logs, driver behavior patterns, and peripheral device interactions, practitioners can identify attack chains that attempt to trigger race windows through rapid HID event generation, detect unusual memory access patterns from kernel space, and correlate timing anomalies with device communication events—ultimately catching exploitation attempts before they reach post-compromise techniques.
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-99313. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation