A buffer overflow vulnerability in the Yenkee Hornet Gaming Mouse driver allows a local attacker to cause a denial of service, resulting in a system crash.

The driver (GM312Fltr.sys) fails to properly validate input length when handling DeviceIoControl requests. By sending a 2000-byte buffer to the driver, a local, low-privileged attacker can trigger a stack-based buffer overflow, resulting in a kernel-level denial of service.

Successful exploitation of this vulnerability results in a complete system crash, leading to unplanned downtime and loss of availability for the affected workstation. Given the CVSS score of 7.5, this is a significant security concern for enterprise environments where driver stability and system uptime are critical. While the impact is primarily a denial of service, kernel-level flaws can often be leveraged for more severe outcomes, such as privilege escalation, if the overflow is weaponized beyond a simple crash.

Immediate Action: As no patch is currently available, users should restrict local access to systems using this hardware and consider disabling or uninstalling the affected driver if it is not business critical.

Proactive Monitoring: Monitor system logs for repeated "DRIVER_OVERRAN_STACK_BUFFER" (0xF7) bugchecks or unusual system instability associated with the GM312Fltr.sys module.

Compensating Controls: Implement endpoint security policies that restrict the ability of low-privileged users to interact with raw device drivers or load unsigned kernel modules.

Public Exploit Available: Yes, a proof-of-concept Python script is available via ExploitDB (EDB-ID: 50311) and the Quadron Research Lab GitHub repository.

Organizations should prioritize identifying systems where the Yenkee Hornet Gaming Mouse is deployed. Due to the lack of a vendor-provided fix and the availability of a functional proof-of-concept exploit, the most effective mitigation is to restrict access or remove the vulnerable driver from sensitive systems until an official patch is released by the manufacturer.