CVE-2015-0058 is a double-free vulnerability in the Windows kernel-mode driver win32k.sys, referred to by Microsoft as the Windows Cursor Object Double Free Vulnerability. The flaw affects Microsoft Windows 8.1, Windows Server 2012 R2, and Windows RT 8.1. According to the provided content, improper handling of a cursor object can cause the same memory to be freed twice in kernel context. A local attacker can trigger the condition via a crafted application after logon. Microsoft bulletin 3036220 identifies this as a Win32k issue in the kernel-mode graphics subsystem.
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.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A historical Win32K subsystem vulnerability referenced as an example of a high-profile flaw that was actively exploited.
An elevation of privilege vulnerability in the Windows kernel-mode driver (win32k.sys) caused by a double-free condition that can lead to arbitrary code execution in kernel mode.
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.