CVE-2020-0069: Local privilege escalation in MediaTek Command Queue driver
- Vendors
- GoogleHuawei Technologies
CVE-2020-0069 is an out-of-bounds write vulnerability in the ioctl handlers of the MediaTek Command Queue driver in the Android kernel. Insufficient input sanitization and missing SELinux restrictions allow local privilege escalation without additional execution privileges or user interaction. The AbstractEmu Android malware family exploited this vulnerability as part of its rooting functionality.
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.
Successful exploitation can elevate an unprivileged local execution context to privileged access on an affected Android device. AbstractEmu used this vulnerability among its rooting exploits; the campaign's resulting root access enabled silent software installation, permission grants, security-setting changes, and access to other applications' sensitive data. The precise privileges and memory-corruption effects of this individual exploit are not further specified.
Mitigation
If you can’t patch tonight, do this now.
Mitigation includes applying the latest Android security updates, restricting app installations to trusted sources (such as the Google Play Store), and monitoring for indicators of compromise. Enterprises should enforce mobile device management policies to prevent installation of untrusted apps and monitor for signs of rooting or privilege escalation.
Remediation
Patch, then assume compromise.
The vulnerability was addressed by Google and Mediatek via security updates to the Android kernel, which included proper input validation in the ioctl handlers and improved SELinux policy enforcement. Users should update their devices to the latest available security patch level to remediate this vulnerability.
Exploits
3 exploits validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit.
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.
References
Frequently asked questions
- Is CVE-2020-0069 exploited in the wild?
- Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Nov 3, 2021.
- Is there a public exploit for CVE-2020-0069?
- Yes. Mallory tracks 3 public exploits or proofs of concept for CVE-2020-0069, the earliest disclosed Sep 6, 2019.
- Is there a patch for CVE-2020-0069?
- The vulnerability was addressed by Google and Mediatek via security updates to the Android kernel, which included proper input validation in the ioctl handlers and improved SELinux policy enforcement. Users should update their devices to the latest available security patch level to remediate this vulnerability.
- What products are affected by CVE-2020-0069?
- Google Android, Huawei Technologies Berkeley-L09 Firmware, Huawei Technologies Columbia-Al10b Firmware, Huawei Technologies Columbia-L29d Firmware, Huawei Technologies Columbia-Tl00b Firmware, and at least 24 more.
- How severe is CVE-2020-0069?
- CVE-2020-0069 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 1.4% (73rd percentile) as of Oct 16, 2026.
Recent activity
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.