Unauthenticated privilege escalation via U-Boot shell
Published Dec 11, 2023 · Updated Feb 25, 2026
Elevation of privilege in Google Android SoC allows remote attackers to gain higher privileges via a U-Boot shell flaw. The vendor identifies the vulnerable locus as the U-Boot shell but does not disclose the incorrect operation or input-handling mechanism. Exploitation therefore requires access to the affected production device path, and the published record bounds the consequence to privilege escalation without documenting additional impact details.
Summary
What happened
Elevation of privilege in Google Android SoC allows remote attackers to gain higher privileges via a U-Boot shell flaw. The vendor identifies the vulnerable locus as the U-Boot shell but does not disclose the incorrect operation or input-handling mechanism. Exploitation therefore requires access to the affected production device path, and the published record bounds the consequence to privilege escalation without documenting additional impact details.
The record
- CVE
- CVE-2023-48424
- Published
- Dec 11, 2023
- Updated
- Feb 25, 2026
- Vendor
- Product
- Android
- Classifications
- T1068
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 11, 2023CVE publishedPublication date reported by the CVE source.
- Feb 25, 2026Record 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 SoC
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