Local privilege escalation via VCU race condition
Published Nov 8, 2022 · Updated May 1, 2025
A race condition in the VCU component on affected MediaTek chipsets running Android 11.0 through 13.0 allows local users to escalate privileges. MediaTek identifies the VCU as the locus and improper synchronization of a shared resource as the corrupting race, but publishes no function or memory-object detail. Exploitation is local, requires System execution privileges, and needs no user interaction; the vendor reports privilege escalation without a finer post-escalation boundary.
Summary
What happened
A race condition in the VCU component on affected MediaTek chipsets running Android 11.0 through 13.0 allows local users to escalate privileges. MediaTek identifies the VCU as the locus and improper synchronization of a shared resource as the corrupting race, but publishes no function or memory-object detail. Exploitation is local, requires System execution privileges, and needs no user interaction; the vendor reports privilege escalation without a finer post-escalation boundary.
The record
- CVE
- CVE-2022-32613
- Published
- Nov 8, 2022
- Updated
- May 1, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-662, CAPEC-26, T1404
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Nov 8, 2022CVE publishedPublication date reported by the CVE source.
- May 1, 2025Record 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Weakness, pattern, technique
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