Four-byte stack disclosure via unchecked secure register
Published Jun 13, 2024 · Updated Nov 1, 2024
Out-of-bounds read in the ACPM set_secure_reg function in Google Android kernel allows local users to disclose four bytes of stack memory. The function in sac_handler.c reads a secure-register value without first checking the input bounds, exposing adjacent stack data. Exploitation requires local low-privileged access to an affected Pixel device but no user interaction or additional execution privileges; the reported consequence is limited to four disclosed bytes.
Summary
What happened
Out-of-bounds read in the ACPM set_secure_reg function in Google Android kernel allows local users to disclose four bytes of stack memory. The function in sac_handler.c reads a secure-register value without first checking the input bounds, exposing adjacent stack data. Exploitation requires local low-privileged access to an affected Pixel device but no user interaction or additional execution privileges; the reported consequence is limited to four disclosed bytes.
The record
- CVE
- CVE-2024-32920
- Published
- Jun 13, 2024
- Updated
- Nov 1, 2024
- Vendor
- Product
- Android
- Classifications
- CWE-125
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 13, 2024CVE publishedPublication date reported by the CVE source.
- Nov 1, 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?
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