CVE-2021-41285
Description
Ballistix MOD Utility through 2.0.2.5 is vulnerable to privilege escalation in the MODAPI.sys driver component. The vulnerability is triggered by sending a specific IOCTL request that allows low-privileged users to directly interact with physical memory via the MmMapIoSpace function call (mapping physical memory into a virtual address space). Attackers could exploit this issue to achieve local privilege escalation to NT AUTHORITY\SYSTEM.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Crucial Ballistix MOD Utility ≤2.0.2.5 includes a driver (MODAPI.sys) that lets low-privileged users map physical memory via an IOCTL, enabling local privilege escalation to SYSTEM.
Vulnerability
CVE-2021-41285 affects the Ballistix MOD Utility version 2.0.2.5 and earlier. The vulnerability resides in the MODAPI.sys driver component, which is a copy of the open-source WinRing0x64.sys driver. The driver exposes multiple IOCTL handlers that allow low-privileged users to call the MmMapIoSpace function, mapping physical memory into a virtual address space. Additionally, it permits reading/writing Model-Specific Registers (MSRs) via __readmsr/__writemsr and IO port access [1][2]. No specific configuration beyond having the driver installed is required for the code path to be reachable.
Exploitation
An attacker with low-privileged user access on the target system can send a crafted IOCTL request to the MODAPI.sys driver. The exploit leverages the MapPhysicalMemory primitive to achieve a write-what-where condition, and the Write MSRs primitive for pointer overwrite. Public proof-of-concept code is available that demonstrates memory dumping and privilege escalation [2]. No additional user interaction is needed; the attack is performed from user land against the kernel driver.
Impact
Successful exploitation allows an attacker to escalate privileges from a low-privileged user to NT AUTHORITY\SYSTEM. The attacker can gain arbitrary read/write access to physical memory, enabling full control over the operating system, including process manipulation, data theft, and persistence [1].
Mitigation
The Ballistix MOD Utility version 2.0.2.5 is the last affected version; the vendor has not released a patch (the driver is derived from an open-source project with known vulnerabilities). Users are advised to uninstall the software or restrict access to the driver via a blocklist. The CVE is not listed in the known exploited vulnerabilities (KEV) catalog as of the publication date [1].
AI Insight generated on May 27, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2- Ballistix/MOD Utilitydescription
- Range: <=2.0.2.5
Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
2News mentions
0No linked articles in our index yet.