CVE-2020-11253
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 · uneditedArbitrary memory write issue in video driver while setting the internal buffers in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile
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 · moderate confidenceA memory corruption vulnerability exists in the Qualcomm video driver where improper validation during internal buffer setup allows an attacker to write to arbitrary memory locations. This arbitrary memory write primitive can lead to privilege escalation and code execution at the kernel/driver level.
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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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 Qualcomm firmware components in your environmentReview hardware/firmware inventory or use system commands (such as 'dmidecode', 'lspci', or device-specific queries) to enumerate installed Qualcomm components. Look specifically for: Aqt1000, Pm3003a, Pm6150, Pm6150a, Pm6150l, Pm6350, Pm7150a, or Pm7150l firmware modules.Affected if Any of these eight firmware components (Aqt1000, Pm3003a, Pm6150, Pm6150a, Pm6150l, Pm6350, Pm7150a, Pm7150l) are present in the system or device.
-
Verify video driver is loaded or activeCheck if the Qualcomm video driver module is currently loaded or active on the system. On Linux-based systems, use commands such as 'lsmod' or 'modinfo' to query video driver modules. On Android, check via 'getprop' or '/proc/modules'.Affected if The Qualcomm video driver module is loaded and actively running.
-
Confirm firmware versionQuery the firmware version of the identified Qualcomm component using vendor-specific tools, device diagnostic interfaces, or by reading firmware metadata. For PMIC components (Pm* series), use appropriate power management IC diagnostic commands if available.Affected if The firmware version cannot be determined or is older than vendor-provided patched versions (all versions of the listed products are affected).
If your environment contains any of the listed Qualcomm firmware components (Aqt1000, Pm3003a, Pm6150, Pm6150a, Pm6150l, Pm6350, Pm7150a, Pm7150l) and the video driver is active, you are potentially affected by this vulnerability.
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 the vendor-provided security patch for the video driver; this requires obtaining the updated driver from Qualcomm and deploying it through device manufacturer firmware updates.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11253 — 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-11253 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