Memory corruption via repeated SMEM entry access
Published Dec 2, 2024 · Updated Dec 3, 2024
Buffer over-read in Qualcomm Snapdragon MProc firmware allows local users to corrupt memory through repeated SMEM partition entry access. Qualcomm identifies the operation as continuous allocation and access of an SMEM entry but has not disclosed the affected function or exact bounds error. Local execution without prior privileges is required, and testing the condition can corrupt component memory.
Summary
What happened
Buffer over-read in Qualcomm Snapdragon MProc firmware allows local users to corrupt memory through repeated SMEM partition entry access. Qualcomm identifies the operation as continuous allocation and access of an SMEM entry but has not disclosed the affected function or exact bounds error. Local execution without prior privileges is required, and testing the condition can corrupt component memory.
The record
- CVE
- CVE-2024-33056
- Published
- Dec 2, 2024
- Updated
- Dec 3, 2024
- Vendor
- Qualcomm
- Product
- Qualcomm Snapdragon 1200 Wearable Platform Firmware
- Classifications
- CWE-126
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 2, 2024CVE publishedPublication date reported by the CVE source.
- Dec 3, 2024Record 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=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