Local privilege escalation via unchecked strncpy write
Published Mar 11, 2024 · Updated Apr 16, 2025
Out-of-bounds write in Android 13 Little Kernel allows local users to escalate privileges through the strncpy implementation. The strncpy function in strncpy.c copies into a destination buffer without the required bounds check, permitting memory past the buffer to be overwritten. Exploitation requires local low-privilege access but no user interaction; Google has not published the private patch or exact input path.
Summary
What happened
Out-of-bounds write in Android 13 Little Kernel allows local users to escalate privileges through the strncpy implementation. The strncpy function in strncpy.c copies into a destination buffer without the required bounds check, permitting memory past the buffer to be overwritten. Exploitation requires local low-privilege access but no user interaction; Google has not published the private patch or exact input path.
The record
- CVE
- CVE-2024-27224
- Published
- Mar 11, 2024
- Updated
- Apr 16, 2025
- Vendor
- Product
- Android
- Classifications
- CWE-269, T1404
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 11, 2024CVE publishedPublication date reported by the CVE source.
- Apr 16, 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=13
- Affected versionversion=13.0
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