Local privilege escalation via unchecked hardware-port write
Published Jun 22, 2021 · Updated Aug 3, 2024
Out-of-bounds write in Android's Knowles IAXXX kernel driver allows local users to escalate privileges through the codec interface. iaxxx_calc_i2s_div in iaxxx-codec.c writes user-controlled data to a hardware port without first enforcing the required bounds. A low-privileged local context is required, user interaction is unnecessary, and successful exploitation can gain kernel-level privileges.
Summary
What happened
Out-of-bounds write in Android's Knowles IAXXX kernel driver allows local users to escalate privileges through the codec interface. iaxxx_calc_i2s_div in iaxxx-codec.c writes user-controlled data to a hardware port without first enforcing the required bounds. A low-privileged local context is required, user interaction is unnecessary, and successful exploitation can gain kernel-level privileges.
The record
- CVE
- CVE-2021-0607
- Published
- Jun 22, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-787, T1404
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 22, 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?
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