Memory corruption via improper RPM XPU configuration
Published Apr 7, 2021 · Updated Aug 4, 2024
Memory corruption in Qualcomm Snapdragon firmware allows local users to corrupt protected RPM memory through an XPU configuration error. The RPM protection setup programs the XPU with an improper policy, leaving the region exposed across its intended protection boundary. Exploitation requires local access but no authentication or user interaction, and successful exploitation can expose or alter protected data or interrupt device operation.
Summary
What happened
Memory corruption in Qualcomm Snapdragon firmware allows local users to corrupt protected RPM memory through an XPU configuration error. The RPM protection setup programs the XPU with an improper policy, leaving the region exposed across its intended protection boundary. Exploitation requires local access but no authentication or user interaction, and successful exploitation can expose or alter protected data or interrupt device operation.
The record
- CVE
- CVE-2020-11210
- Published
- Apr 7, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 7, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
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.
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