Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2012-6422: ExynosAbuse: Insecure Permissions on /dev/exynos-mem in Samsung/MEIZU Android Devices

Published Dec 18, 2012 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.3Critical · v2
EPSS15.1%97th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendors
Samsung ElectronicsMeizu
IdentifiersCVE-2012-6422CWE-732

A vulnerability in the kernel of Samsung Galaxy S2, Galaxy Note 2, MEIZU MX, and potentially other Android devices using Exynos 4210 or 4412 processors, where the device node /dev/exynos-mem is created with world-readable and writable permissions (0666). This allows any application to read or write arbitrary physical memory, enabling privilege escalation and arbitrary code execution. The issue was exploited by the ExynosAbuse exploit.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Attackers can gain root privileges on affected devices by exploiting the weak permissions on /dev/exynos-mem, leading to full compromise of the device, including arbitrary code execution in kernel context, bypassing all userland security controls.

Mitigation

If you can’t patch tonight, do this now.

Restrict installation of untrusted applications, use application whitelisting, and monitor for suspicious activity. Until a patch is available, users can manually change the permissions on /dev/exynos-mem after each boot, though this is not a persistent or comprehensive solution.

Remediation

Patch, then assume compromise.

Update the device kernel to a version where /dev/exynos-mem is created with restrictive permissions (e.g., 0600 or 0604), or remove the device node entirely if not required. Device manufacturers have released patches to address this issue in later firmware updates.

Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →
CVE-2012-6422This repository is a small local privilege-escalation proof of concept for older Samsung Exynos-based Android devices affected by insecure permissions on /dev/exynos-mem. It contains two files: a README describing the technique and one C source file, r00ter.c, which implements the exploit logic. The exploit is not network-facing; it is a local attack that assumes an unprivileged user can access the vulnerable exynos-mem interface. The code relies on a separate local helper executable, ./exynos-mem, which it invokes with popen() to read and write arbitrary physical memory. The exploit scans a configured kernel physical memory range for the kallsyms format string "%pK %c %s\n" and patches it to "%p ", weakening kernel pointer restrictions so /proc/kallsyms reveals symbol addresses to a non-root user. After disclosure is enabled, the exploit parses /proc/kallsyms to locate the kernel symbol nsown_capable. It then translates that virtual symbol address into a physical address using hardcoded kernel offsets and overwrites the function body with a short ARM stub that simply returns true. This bypasses capability checks relevant to setuid(), allowing the process to call setuid(0), become root, and execute /bin/sh. Repository structure is minimal and purpose-built: README.md explains the vulnerability and exploitation steps; r00ter.c contains helper routines for memory read/write, scanning and patching the kallsyms format string, symbol extraction, kernel function patching, and the main privilege-escalation flow. The exploit is operational but device-specific, as the kernel memory boundaries and offsets are hardcoded and may need tuning per target.wired0ut · Disclosed Aug 30, 2025 · c · markdown · localOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
MeizuMxhardware
Samsung ElectronicsGalaxy Note 2hardware
Samsung ElectronicsGalaxy S2hardware
FAQ

Frequently asked questions

Is CVE-2012-6422 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2012-6422?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2012-6422, the earliest disclosed Aug 30, 2025.
Is there a patch for CVE-2012-6422?
Update the device kernel to a version where /dev/exynos-mem is created with restrictive permissions (e.g., 0600 or 0604), or remove the device node entirely if not required. Device manufacturers have released patches to address this issue in later firmware updates.
What products are affected by CVE-2012-6422?
Meizu Mx, Samsung Electronics Galaxy Note 2, and Samsung Electronics Galaxy S2.
How severe is CVE-2012-6422?
CVE-2012-6422 has a CVSS v2 score of 9.3 (Critical) and an EPSS score of 15.1% (97th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware1Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.