CVE-2020-11246
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 · uneditedA double free condition can occur when the device moves to suspend mode during secure playback 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 double free vulnerability exists in the secure playback subsystem of Qualcomm Snapdragon chipsets. When a device enters suspend mode during active secure playback, memory allocated for the secure playback session is freed, but the pointer is not nullified. If the suspend/resume cycle attempts to access or free this already-freed memory, a double free condition occurs, leading to potential memory corruption and potential code execution.
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 the device chipset modelCheck the processor information using /proc/cpuinfo or device system information settings to determine the exact Snapdragon or Qualcomm chipset modelAffected if The chipset model matches one of the affected variants: Apq8017, Apq8037, Apq8053, Aqt1000, Msm8917, Msm8920, Msm8937, or Msm8940
-
Verify firmware version availabilityCheck the baseband or modem firmware version through AT commands (AT+CGMR) or system settings under About Phone > Baseband versionAffected if The firmware version cannot be verified or was released prior to the Qualcomm security patch date for CVE-2020-11246
-
Confirm secure playback capabilityDetermine if the device supports DRM-protected or secure media playback (such as Widevine L1 or hardware DRM) by checking DRM service informationAffected if The device supports and has active secure playback features enabled
-
Test suspend behavior during secure playbackInitiate a secure media playback session (DRM-protected content), then trigger device suspend/sleep mode, and observe for system instability or crash logs during resumeAffected if The device enters suspend mode while secure playback is active and exhibits unexpected behavior or memory errors upon resume
The device is affected if it uses one of the listed Qualcomm chipsets and supports secure playback, as the double-free vulnerability triggers during suspend/resume cycles with active secure media sessions.
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 firmware/security patch from Qualcomm for the affected Snapdragon chipset. Until the patch is available, avoid putting devices into suspend mode during active secure media playback sessions.
- 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-11246 — 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-11246 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