Loading vulnerability…
Information currently not available.
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.
Repository contains two Windows local privilege escalation PoCs targeting CVE-2025-66678 in “Hardware Read & Write Utility v1.25.11.26”, where the bundled driver exposes powerful IOCTL primitives: (1) arbitrary MSR read/write and (2) arbitrary physical memory read/write via MmMapIoSpace. Structure/purpose: - HardwareEditorRWMSR/ (Visual Studio solution + C++ + x64 MASM): Implements an MSR-based kernel execution technique. It opens the vulnerable device (\\.\HwRwDrv) and uses IOCTLs 0x9C402084/0x9C402088 to read/write MSRs. The exploit overwrites MSR_LSTAR (0xC0000082) to point to a kernel ROP gadget (swapgs; iretq) computed from ntoskrnl.exe base + hardcoded offsets. It then triggers a syscall from user mode (PrepareStack.asm) to enter the gadget chain, disables SMEP/SMAP (CR4/RFLAGS manipulation), runs ring0 token-stealing shellcode (walks ActiveProcessLinks to PID 4 and copies its token to the current EPROCESS), restores MSR_LSTAR to the original KiSystemCall64Shadow, and returns to user mode. Finally it launches cmd.exe. - HardwareEditorRWPhys/ (Visual Studio solution + C++): Implements a physical-memory read/write based LPE using IOCTLs 0x9C406104/0x9C40A108. The code includes Windows build-based EPROCESS offset selection (UniqueProcessId/ActiveProcessLinks) and additional logic (truncated in provided view) consistent with locating kernel structures/functions and patching memory to achieve token theft/elevation. - README.md: Documents the vulnerability, states the driver is not included, and provides usage steps (place HwRwDrv.sys in C:\Users\Public and run as Administrator). Overall capability: reliable local SYSTEM elevation on vulnerable systems by abusing a kernel driver’s exposed IOCTLs to gain kernel code execution and swap the current process token to SYSTEM.
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.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.