Local privilege escalation via audio use-after-free
Published Dec 16, 2022 · Updated Apr 18, 2025
Use-after-free in aud_hal_tunnel.c in the Android kernel allows local users to gain elevated privileges through audio processing. The Pixel Audio component dereferences memory after its lifetime ends in the audio HAL tunnel path, corrupting kernel memory. A low-privileged local user can reach the flaw without user interaction, and successful exploitation grants privileges beyond the initiating process.
Summary
What happened
Use-after-free in aud_hal_tunnel.c in the Android kernel allows local users to gain elevated privileges through audio processing. The Pixel Audio component dereferences memory after its lifetime ends in the audio HAL tunnel path, corrupting kernel memory. A low-privileged local user can reach the flaw without user interaction, and successful exploitation grants privileges beyond the initiating process.
The record
- CVE
- CVE-2022-20561
- Published
- Dec 16, 2022
- Updated
- Apr 18, 2025
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-416, T1404
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 16, 2022CVE publishedPublication date reported by the CVE source.
- Apr 18, 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 kernel
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