CVE-2020-11295
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 · uneditedUse after free in camera If the threadmanager is being cleaned up while the worker thread is processing objects 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 use-after-free vulnerability exists in the camera subsystem where the ThreadManager cleanup operation races with the worker thread processing objects. When the ThreadManager is being cleaned up while the worker thread is still accessing objects, freed memory can be dereferenced, leading to potential code execution or denial of service.
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 device and Qualcomm componentsDetermine the exact device/model and verify it contains any of the following Qualcomm components: Fsm10055, Fsm10056, Pm3003a, Pm6125, Pm6150, Pm6150a, Pm6150l, or Pm6350 firmware. Consult device hardware specifications or vendor documentation.Affected if The device contains any of the listed Qualcomm firmware components in the camera subsystem.
-
Check firmware version of affected componentsAccess the device's firmware/diagnostics information to retrieve the installed version of the Qualcomm camera subsystem firmware (FSM or PMIC components). This may be available through manufacturer tools, device diagnostic menus, or by querying /proc or system files if root access is available.Affected if The installed firmware version matches one of the affected products and no vendor patch has been applied.
-
Verify camera subsystem is activeConfirm the camera subsystem is enabled and in use on the device. Check if camera applications or camera-related services are running and actively using the ThreadManager component.Affected if The camera subsystem is actively running and the ThreadManager cleanup race condition can be triggered.
-
Check for vendor firmware bulletinsReview the device manufacturer's security advisories or firmware release notes to see if CVE-2020-11295 is specifically addressed and whether a patched firmware version is available for the device.Affected if The manufacturer has not released a security patch for this CVE or the installed firmware predates the patch date.
A defender is affected if their device contains any of the listed Qualcomm firmware components (Fsm10055/10056, Pm3003a/6125/6150/6150a/6150l/6350) in the camera subsystem and the vendor has not released a security patch addressing this use-after-free 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 vendor-supplied firmware/security patches from the device manufacturer addressing the Qualcomm Snapdragon camera ThreadManager use-after-free vulnerability. Users should monitor for and apply available OTA updates.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11295 — 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-11295 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