CVE-2023-48425Public exploit

Persistent unsigned-code execution via trusted upgrade-step value

Published Dec 11, 2023 · Updated May 27, 2025

Secure Boot bypass in U-Boot on Google Android SoC devices allows physically proximate attackers to execute persistent unsigned code. The AVB verification path trusts the writable upgrade_step environment value and treats value 3 as both permission to ignore verification errors and a successful verification result. The demonstrated chain requires physical eMMC fault injection to obtain a U-Boot shell; it can then boot modified images while Android reports the device as locked and secure.

CVSS severity9.8
Critical
EPSS probability0.37%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Secure Boot bypass in U-Boot on Google Android SoC devices allows physically proximate attackers to execute persistent unsigned code. The AVB verification path trusts the writable upgrade_step environment value and treats value 3 as both permission to ignore verification errors and a successful verification result. The demonstrated chain requires physical eMMC fault injection to obtain a U-Boot shell; it can then boot modified images while Android reports the device as locked and secure.

The record

CVE
CVE-2023-48425
Published
Dec 11, 2023
Updated
May 27, 2025
Vendor
Google
Product
Android
Classifications
CWE-20, T1553.006, T1542.003
Attack vector
physical
Privileges
unauthenticated

Timeline

How it unfolded

  1. Dec 11, 2023CVE publishedPublication date reported by the CVE source.
  2. May 27, 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.

  1. Affected versionversion=Android SoC

What conditions does exploitation require?

Attack vectorphysical
Required privilegesunauthenticated

What is affected?

Google · Androidversion=Android SoC

Published CVSS scores

9.8CISA-ADPCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
9.8NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorphysical
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-20Improper Input Validation
T1553.006Code Signing Policy Modification
T1542.003Bootkit

Public exploit references

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