CVE-2020-0069 remediation guide

MediaTek Multiple Chipsets

In the ioctl handlers of the Mediatek Command Queue driver, there is a possible out of bounds write due to insufficient input sanitization and missing SELinux restrictions. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-147882143References: M-ALPS04356754

Open CVE record

ProductMediaTek Multiple Chipsets

Affected versionsAndroid kernel, < 10.0.0.177\(c10e3r1p4\), < 10.0.0.178\(c00e178r1p4\), < 10.0.0.177\(c10e4r1p4\), < 10.0.0.178\(c01e178r1p4\), < 9.1.0.340\(c00e333r1p1t8\), < 9.1.0.340\(c01e333r1p1t8\), < 1.0.0.190\(c00\), < 10.0.0.194\(c636e3r3p1\), < 9.1.0.290\(c185e5r4p1\), < 9.1.0.338\(c00e333r1p1t8\), < 10.0.0.160\(c01e32r2p4\), < 9.1.0.291\(c185e3r4p1\), < 10.0.0.198\(c432e10r3p4\), < 9.1.0.251\(c00e106r2p2\), < 9.1.0.146\(c00e131r2p2\), < 9.1.0.160\(c00e150r1p7\), < 9.1.0.261\(c00e120r4p1\), < 9.1.0.380\(c636e1r1p3t8\), < 10.0.0.194\(c00e61r4p11\)

Fixed versions10.0.0.177\(c10e3r1p4\), 10.0.0.178\(c00e178r1p4\), 10.0.0.177\(c10e4r1p4\), 10.0.0.178\(c01e178r1p4\), 9.1.0.340\(c00e333r1p1t8\), 9.1.0.340\(c01e333r1p1t8\), 1.0.0.190\(c00\), 10.0.0.194\(c636e3r3p1\), 9.1.0.290\(c185e5r4p1\), 9.1.0.338\(c00e333r1p1t8\), 10.0.0.160\(c01e32r2p4\), 9.1.0.291\(c185e3r4p1\), 10.0.0.198\(c432e10r3p4\), 9.1.0.251\(c00e106r2p2\), 9.1.0.146\(c00e131r2p2\), 9.1.0.160\(c00e150r1p7\), 9.1.0.261\(c00e120r4p1\), 9.1.0.380\(c636e1r1p3t8\), 10.0.0.194\(c00e61r4p11\), 9.1.0.237\(c00e80r1p7t8\)

Priority basisImmediate · CVSS 7.8 · EPSS 1.30%

Identify the affected asset

Confirm whether MediaTek Multiple Chipsets is installed, record the deployed version and installation path, and identify exposed interfaces.

Record the product name, package or appliance identifier, and installed version.
Identify internet-facing, administrative, API, and internal access paths.
Preserve the pre-change configuration and relevant service logs.

Validate the affected-version match

Compare the deployed version with the affected range: Android kernel, < 10.0.0.177\(c10e3r1p4\), < 10.0.0.178\(c00e178r1p4\), < 10.0.0.177\(c10e4r1p4\), < 10.0.0.178\(c01e178r1p4\), < 9.1.0.340\(c00e333r1p1t8\), < 9.1.0.340\(c01e333r1p1t8\), < 1.0.0.190\(c00\), < 10.0.0.194\(c636e3r3p1\), < 9.1.0.290\(c185e5r4p1\), < 9.1.0.338\(c00e333r1p1t8\), < 10.0.0.160\(c01e32r2p4\), < 9.1.0.291\(c185e3r4p1\), < 10.0.0.198\(c432e10r3p4\), < 9.1.0.251\(c00e106r2p2\), < 9.1.0.146\(c00e131r2p2\), < 9.1.0.160\(c00e150r1p7\), < 9.1.0.261\(c00e120r4p1\), < 9.1.0.380\(c636e1r1p3t8\), < 10.0.0.194\(c00e61r4p11\). Treat incomplete inventory results as unresolved.

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

Apply supported remediation

Apply updates per vendor instructions.

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

Confirm the expected version and package state.
Run a functional health check for critical service paths.
Review authentication, error, application, and security monitoring logs.
Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.