Loading vulnerability…
The BS_RCIO64.sys driver in Biostar RACING GT Evo 2.1.1905.1700 exposes device objects to low-integrity processes, allowing them to issue IOCTLs (0x226040, 0x226044, 0x226000) that enable reading and writing to arbitrary physical memory locations or calling arbitrary addresses. This allows unprivileged users to execute code in kernel context, leading to full system compromise.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a proof-of-concept (POC) local privilege escalation exploit for CVE-2021-44852, targeting the Biostar RACING GT Evo 2.1.1905.1700 driver (BS_RCIO64.sys) on Windows 7 SP1 x64-86. The exploit is implemented in C (exploit.c) and uses custom x64 kernel shellcode (shellcode.asm) to manipulate kernel structures and elevate privileges. The exploit works by opening a handle to the vulnerable device (\\.\GLOBALROOT\Device\BS_RCIO), allocating executable memory for the shellcode, and triggering the vulnerability via a crafted IOCTL (0x226000) using DeviceIoControl. The shellcode is designed to locate the SYSTEM process and manipulate its token, enabling privilege escalation. The project is structured as a Visual Studio C++ solution with supporting project files, a C header (exploit.h), and a README describing the vulnerability and exploitation approach. The exploit is currently a POC and may require further development for full operational use.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.