CVE-2012-6422

CVE-2012-6422 is a critical-severity vulnerability in Meizu Mx with a CVSS 2.0 base score of 9.3. Its EPSS exploit-prediction score of 15% places it in the 96th percentile, indicating an elevated likelihood of exploitation. The underlying weakness is classified as CWE-264.

Key facts

Description

The kernel in Samsung Galaxy S2, Galaxy Note 2, MEIZU MX, and possibly other Android devices, when running an Exynos 4210 or 4412 processor, uses weak permissions (0666) for /dev/exynos-mem, which allows attackers to read or write arbitrary physical memory and gain privileges via a crafted application, as demonstrated by ExynosAbuse.

Frequently asked questions

What is CVE-2012-6422?
The kernel in Samsung Galaxy S2, Galaxy Note 2, MEIZU MX, and possibly other Android devices, when running an Exynos 4210 or 4412 processor, uses weak permissions (0666) for /dev/exynos-mem, which allows attackers to read or write arbitrary physical memory and gain privileges via a crafted application, as demonstrated by ExynosAbuse.
How severe is CVE-2012-6422?
CVE-2012-6422 has a CVSS 2.0 base score of 9.3, rated critical severity.
Is CVE-2012-6422 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 15% (96th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2012-6422?
CVE-2012-6422 primarily affects Meizu Mx. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2012-6422?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2012-6422 published?
CVE-2012-6422 was published on 2012-12-18 and last updated on 2026-06-16.

References

Affected products (3)

Other CWE-264 (Permissions, Privileges, and Access Controls) vulnerabilities

Browse all CWE-264 (Permissions, Privileges, and Access Controls) vulnerabilities →