Loading vulnerability…
CVE-2012-5525 is a vulnerability in the get_page_from_gfn hypercall function in Xen 4.2. The flaw allows a local paravirtualized (PV) guest OS administrator to trigger a buffer over-read by supplying a specially crafted guest frame number (GFN). This can result in the hypervisor reading memory beyond the intended buffer boundary, leading to a crash of the Xen host.
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 single Metasploit post-exploitation module targeting a denial-of-service (DoS) vulnerability in Xen hypervisor version 4.2.0 (CVE-2012-5525). The module is written in Ruby and is designed to be run from a paravirtualized Linux VM (including dom0) with root privileges. It checks for the presence of required build tools and the correct Xen version, then dynamically generates a C source file and Makefile for a malicious Linux kernel module (LKM). The module compiles and loads the LKM, which triggers a hypercall with crafted arguments to crash the Xen hypervisor, resulting in a DoS condition. The exploit is operational and requires local access with root privileges. The main fingerprintable endpoints are file paths used for temporary storage and for checking Xen's running state. The structure is typical for a Metasploit module, with clear separation of requirements checking, payload generation, and execution logic.
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.