CVE-2020-11210
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPossible memory corruption in RPM region due to improper XPU configuration in Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMemory corruption vulnerability in the RPM (Resource Power Manager) region of Qualcomm Snapdragon chips caused by improper XPU (protection unit) configuration. This allows potential arbitrary memory writes in a critical low-level system component, potentially leading to privilege escalation or system compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device Qualcomm Snapdragon chip modelCheck the device specifications, system-on-chip (SoC) information, or boot logs for the specific Qualcomm Snapdragon model number (e.g., via 'cat /proc/cpuinfo' or manufacturer documentation)Affected if The device uses a Snapdragon SoC that incorporates one of the listed affected PMIC firmware components (Ar8035, Pm4125, Pm4250, Pm6125, Pm6150a, Pm6150l, Pm6350, or Pm7250b)
-
Locate the Power Management IC (PMIC) firmware versionAccess the PMIC/RPM firmware information through device diagnostics, bootloader logs (dmesg, boot logs), or manufacturer-provided firmware version utilities; this often requires root access or manufacturer diagnostic toolsAffected if The PMIC firmware version cannot be determined or shows a firmware version that has not been patched by the OEM after the CVE disclosure date (2020)
-
Verify OEM firmware update statusContact the device manufacturer or check their security advisory pages for the specific device model to confirm whether a firmware patch for CVE-2020-11210 has been appliedAffected if The device manufacturer has not released or applied a security patch addressing this CVE, or the device is running original factory firmware without updates
A user is affected if their device contains a Qualcomm Snapdragon SoC with any of the listed PMIC firmware components (Ar8035, Pm4125, Pm4250, Pm6125, Pm6150a, Pm6150l, Pm6350, Pm7250b) and the OEM has not released or applied a corresponding security patch for CVE-2020-11210.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply firmware security patches released by Qualcomm and distributed through OEM device manufacturers. Organizations should identify and update all affected devices through official vendor channels.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11210 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-11210 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data