CVE-2015-3636 is a use-after-free vulnerability in the Linux kernel's ping_unhash function (net/ipv4/ping.c) prior to version 4.0.3. The vulnerability arises because the function does not properly initialize a list data structure during the unhash operation. Local attackers can exploit this by creating a SOCK_DGRAM socket for IPPROTO_ICMP or IPPROTO_ICMPV6, then disconnecting and reconnecting, leading to use-after-free conditions. This can result in local privilege escalation or denial of service (system crash). The vulnerability is notable for being used in Android privilege escalation exploits, including by advanced spyware such as Skygofree.
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.
3 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a local privilege escalation exploit targeting ARM-based Android devices running a vulnerable Linux kernel. The main files are 'poc.c' (the exploit driver) and 'getroot.c' (the kernel credential manipulation logic). The exploit works by abusing kernel structures and socket manipulation to gain arbitrary kernel read/write, then locates and modifies the current process's credentials to escalate privileges to root. Upon success, it spawns a root shell by executing '/system/bin/sh'. The code is written in C and is intended to be compiled as a static binary for execution on the target device. No network endpoints or remote attack vectors are present; the exploit must be run locally on the device. The repository is structured for Android NDK builds, as indicated by the 'Android.mk' file.
This repository contains a local privilege escalation exploit targeting the Linux kernel, specifically for Android devices. The main exploit logic is implemented in 'exploit.c', which manipulates kernel memory via a race condition involving ICMP sockets (pingpong vulnerability). The exploit creates a large number of sockets and uses memory mapping and process forking to trigger the vulnerability, allowing arbitrary kernel memory read and write. The 'pingpong.c' and 'pingpong.h' files provide an interface for reading and writing kernel memory at arbitrary addresses, and for running the exploit with a callback. The build file 'Android.mk' is used to compile the code as a static library for Android. The exploit is operational and can be used to escalate privileges on vulnerable systems, but does not include a weaponized, customizable payload. The attack vector is local, requiring code execution on the target device. The only fingerprintable endpoint is the use of device files and sockets, typical for kernel exploits.
This repository contains a local privilege escalation exploit targeting ARM-based Android devices running vulnerable Linux kernels. The main files are 'poc.c' (the exploit driver) and 'getroot.c' (the kernel credential modification payload). The exploit works by manipulating kernel memory structures associated with process credentials, ultimately setting all user and group IDs to 0 and granting all capabilities. The exploit then spawns a root shell at '/system/bin/sh'. The attack vector is local, requiring code execution on the target device. The Makefile ('Android.mk') is provided for building the exploit as a static binary. No network endpoints or remote attack surfaces are present; the exploit is purely local. The code is operational and provides a working root shell if the target is vulnerable.
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.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.