Memory corruption during DRM request handling
Published Jun 6, 2023 · Updated Aug 3, 2024
Memory corruption in Qualcomm Linux components on affected Snapdragon chipsets allows local users to corrupt memory through a DRM request. Qualcomm identifies DRM request handling as the trigger but has not disclosed the affected function, buffer operation, or input validation failure. Exploitation requires high local privileges, and the vendor has not published a more specific consequence than memory corruption.
Summary
What happened
Memory corruption in Qualcomm Linux components on affected Snapdragon chipsets allows local users to corrupt memory through a DRM request. Qualcomm identifies DRM request handling as the trigger but has not disclosed the affected function, buffer operation, or input validation failure. Exploitation requires high local privileges, and the vendor has not published a more specific consequence than memory corruption.
The record
- CVE
- CVE-2022-33267
- Published
- Jun 6, 2023
- Updated
- Aug 3, 2024
- Vendor
- Qualcomm
- Product
- SA8155P Firmware
- Classifications
- CWE-119, CWE-787
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 6, 2023CVE publishedPublication date reported by the CVE source.
- Aug 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?
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