Local privilege escalation via m4u use-after-free
Published Sep 27, 2021 · Updated Aug 3, 2024
Use-after-free memory corruption in MediaTek m4u on Android 10.0 and 11.0 allows local users with System privileges to gain elevated execution. The component reuses memory after it has been freed, producing corruption, but MediaTek has not disclosed the triggering input or finer-grained code locus. Exploitation requires prior System execution privileges and no user interaction; exposure is limited to devices using the listed affected chipsets.
Summary
What happened
Use-after-free memory corruption in MediaTek m4u on Android 10.0 and 11.0 allows local users with System privileges to gain elevated execution. The component reuses memory after it has been freed, producing corruption, but MediaTek has not disclosed the triggering input or finer-grained code locus. Exploitation requires prior System execution privileges and no user interaction; exposure is limited to devices using the listed affected chipsets.
The record
- CVE
- CVE-2021-0611
- Published
- Sep 27, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Sep 27, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo