Loading vulnerability…
CVE-2015-6640 is a vulnerability in the prctl_set_vma_anon_name function in kernel/sys.c in Android before 5.1.1 LMY49F and 6.0 before 2016-01-01. The function fails to ensure that only a single VMA (Virtual Memory Area) is accessed during a specific update operation. This flaw allows a crafted application to corrupt the VMA list, potentially leading to privilege escalation or denial of service.
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 is a proof-of-concept (POC) exploit for CVE-2015-6640, targeting the Android kernel's prctl PR_SET_VMA interface. The repository contains a single C source file (jni/main.c) and build scripts for Android NDK (Android.mk, Application.mk). The exploit mmap()s a region of memory, fills it with data, and then uses the prctl syscall with PR_SET_VMA and PR_SET_VMA_ANON_NAME to manipulate the memory mapping's name. It prints the process's memory map before and after the syscall to demonstrate the effect. The code does not provide privilege escalation or a shell, but serves as a demonstration of the vulnerability. The only fingerprintable endpoint is the /proc/self/maps file, which is used to observe the memory mapping changes. The exploit is intended for local execution on a vulnerable Android device or emulator with ARM architecture.
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.