Arbitrary code execution via accessible boot memory
Published Dec 10, 2025 · Updated Dec 10, 2025
Improper access control in U-Boot before 2017.11 on affected Qualcomm IPQ chips allows physically proximate attackers to execute arbitrary code. The bootloader leaves volatile memory containing copied boot code accessible, allowing injected code to run in the pre-OS execution context. Physical access to a device using an affected chip is required; successful exploitation permits attacker-controlled code to run before the operating system starts.
Summary
What happened
Improper access control in U-Boot before 2017.11 on affected Qualcomm IPQ chips allows physically proximate attackers to execute arbitrary code. The bootloader leaves volatile memory containing copied boot code accessible, allowing injected code to run in the pre-OS execution context. Physical access to a device using an affected chip is required; successful exploitation permits attacker-controlled code to run before the operating system starts.
The record
- CVE
- CVE-2025-24857
- Published
- Dec 10, 2025
- Updated
- Dec 10, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-284
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 10, 2025CVE publishedPublication date reported by the CVE source.
- Dec 10, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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