ASUS Armoury Crate CVE-2026-75808

Exploitation requires a local user-level account on the target system (CVSS PR:L) and the ability to interact with the ASUS Armoury Crate kernel driver, meaning Armoury Crate must be installed and its driver loaded. Attack complexity is rated High (AC:H), indicating the attacker must first circumvent the driver's authentication mechanism - this is not a default-exploitable condition and requires understanding of the driver's IOCTL interface or authentication scheme. No network access, no elevated privileges, and no user interaction from a victim are required once the driver authentication is bypassed. Exploitation is limited to denial-of-service on the local machine and cannot propagate to other systems. Systems without Armoury Crate installed are entirely unaffected.

The CVSS 4.0 score of 5.7 (Medium) with vector AV:L/AC:H/AT:N/PR:L/UI:N reflects the realistic constraints of this vulnerability: local access is required and attack complexity is rated High, meaning exploitation is non-trivial and demands the attacker overcome the driver authentication bypass - a condition that is not straightforwardly reproducible. Real-world risk is moderate; even a mid-sized municipal IT team in inowroclaw managing a fleet of ASUS gaming workstations should treat this as a patch-cycle priority rather than an emergency, given that exploitation requires an existing local session and high attack complexity. No EPSS data was supplied, no CISA KEV listing exists, and no public proof-of-concept code has been identified, collectively suggesting this has not been weaponized in active campaigns. The impact is strictly an availability concern - the CVSS vector confirms zero confidentiality or integrity impact - making it chiefly relevant in shared or kiosk environments where a restricted local user could deliberately destabilize the machine for other users. The absence of a scope change (SA:N/SI:N) means the attack cannot propagate to other systems beyond the victim host.

A local user with a standard (low-privilege) account on an ASUS gaming machine running Armoury Crate bypasses the kernel driver's authentication check - likely by crafting or replaying an IOCTL call that mimics an authenticated request - and then issues a loop of memory allocation commands through the driver interface with no enforced quota. System memory is progressively exhausted until the host becomes unresponsive or crashes. No public proof-of-concept exists, but the attack concept is well understood for driver IOCTL interfaces.