The issue arises from improper validation of callback parameters during the creation of a hook procedure in the Windows kernel-mode driver. This allows local users to gain privileges via a crafted application. An attacker who successfully exploits this issue could run arbitrary code in kernel mode, enabling them to install programs, view, change, or delete data, or create new accounts with full user rights.