Local privilege escalation via unreferenced callback object
Published Feb 28, 2023 · Updated Mar 21, 2025
Improper locking in the wificond event loop in Android 12, 12L, and 13 allows local users to escalate privileges. looper_backed_event_loop.cpp creates an EventLoopCallback without sp::make, so the RefBase object does not receive its required initial strong reference and concurrent activity can corrupt memory. A local foothold is required, but no additional execution privileges or user interaction are needed to obtain higher system privileges.
Summary
What happened
Improper locking in the wificond event loop in Android 12, 12L, and 13 allows local users to escalate privileges. looper_backed_event_loop.cpp creates an EventLoopCallback without sp::make, so the RefBase object does not receive its required initial strong reference and concurrent activity can corrupt memory. A local foothold is required, but no additional execution privileges or user interaction are needed to obtain higher system privileges.
The record
- CVE
- CVE-2023-20939
- Published
- Feb 28, 2023
- Updated
- Mar 21, 2025
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-667, T1404
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 28, 2023CVE publishedPublication date reported by the CVE source.
- Mar 21, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Android-12 Android-12L Android-13
What conditions does exploitation require?
What is affected?
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