Memory corruption via malformed fastboot display-mode command
Published Jun 1, 2026 · Updated Jun 1, 2026
Memory corruption in Qualcomm Snapdragon Display allows physically proximate attackers to corrupt memory through a fastboot display-mode command. The command handler processes display-mode input without adequate syntax validation, but Qualcomm has not disclosed the malformed field or unsafe memory operation. Physical access and high privileges are required; the public record does not identify whether corruption causes a crash, code execution, or another outcome.
Summary
What happened
Memory corruption in Qualcomm Snapdragon Display allows physically proximate attackers to corrupt memory through a fastboot display-mode command. The command handler processes display-mode input without adequate syntax validation, but Qualcomm has not disclosed the malformed field or unsafe memory operation. Physical access and high privileges are required; the public record does not identify whether corruption causes a crash, code execution, or another outcome.
The record
- CVE
- CVE-2026-24092
- Published
- Jun 1, 2026
- Updated
- Jun 1, 2026
- Vendor
- Qualcomm
- Product
- Snapdragon
- Classifications
- CWE-1286
- Attack vector
- physical
- Privileges
- admin
Timeline
How it unfolded
- Jun 1, 2026CVE publishedPublication date reported by the CVE source.
- Jun 1, 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=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
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