CVE-2017-11045
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 · uneditedIn Android for MSM, Firefox OS for MSM, QRD Android, with all Android releases from CAF using the Linux kernel, in a camera driver function, a race condition exists which can lead to a Use After Free condition.
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 confidenceA race condition in a camera driver function within Android for MSM (Qualcomm Snapdragon) devices allows an attacker to trigger a Use After Free (UAF) memory corruption condition. The vulnerability exists in the Linux kernel camera driver code, where improper synchronization between threads can lead to memory being accessed after it has been freed.
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 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:H/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.
-
Confirm device uses Qualcomm Snapdragon (MSM) chipsetCheck device specifications or run 'getprop ro.hardware' or 'cat /proc/cpuinfo' to identify the chipset. MSM (Mobile Station Modem) refers to Qualcomm Snapdragon processors.Affected if Device is NOT running on a Qualcomm Snapdragon/MSM chipset - these are the only affected devices
-
Verify Android OS is in useRun 'getprop ro.build.version.release' or check system settings to confirm the operating system is Google Android.Affected if Device is not running Android - this CVE only affects Android devices
-
Check the kernel versionRun 'uname -r' or 'cat /proc/version' to obtain the kernel version. Compare against any vendor-supplied patch information for this CVE.Affected if Kernel version has not received the vendor security patch for CVE-2017-11045 - the vulnerability persists in unpatched kernels
-
Confirm camera driver module is loadedCheck for camera driver presence via 'ls /dev/video*' or 'cat /proc/modules' to list loaded kernel modules related to camera (such as msm_vidc, camera, or videobuf).Affected if Camera driver module is loaded and active - the race condition can only trigger when the camera driver is in use
The device is affected if it runs Android on a Qualcomm Snapdragon (MSM) chipset with an unpatched kernel and has the camera driver loaded/enabled.
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-supplied security patch from Qualcomm/Google for this CVE. Until the patch is available, restrict access to camera functionality and monitor for unusual camera driver behavior.
- Consultation3.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,568.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-11045 — 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-2017-11045 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