Loading vulnerability…
An elevation of privilege vulnerability exists in the Android kernel ION subsystem (affecting Kernel versions 3.10 and 3.18). A local malicious application can exploit this flaw to execute arbitrary code with kernel privileges. The vulnerability is considered critical due to the potential for a local, permanent device compromise, which may require reflashing the operating system to recover.
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) exploit for CVE-2017-0564, a race condition vulnerability in the ION memory allocator on Android devices. The main exploit code is in 'poc.c', which opens the '/dev/ion' device and allocates memory from various ION heaps. It then creates two threads that attempt to free the same ION handle simultaneously, aiming to trigger a race condition in the kernel's ION driver. The exploit is a local privilege escalation PoC and does not include a payload for gaining root or a shell; it is intended to demonstrate the presence of the vulnerability. The repository also includes a build file (Android.mk) and a header (local_poc.h) for ioctl command construction. The only fingerprintable endpoint is the '/dev/ion' device node. The exploit is relevant for Android devices running vulnerable kernels prior to the patch for CVE-2017-0564.
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.