CVE-2016-10383
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 all Qualcomm products with Android releases from CAF using the Linux kernel, there is a TOCTOU race condition in Secure UI.
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 confidenceThis vulnerability is a Time-Of-Check to Time-Of-Use (TOCTOU) race condition存在于高通(Qualcomm)产品的安全用户界面(Secure UI)组件中,影响使用Linux内核的Android CAF(Code Aurora Forum)版本。
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
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/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 processor vendorCheck if the device uses a Qualcomm Snapdragon processor by looking at device specifications in Settings > About Phone > Processor or by checking /proc/cpuinfo for 'Qualcomm' or 'Snapdragon' entriesAffected if Device does not have a Qualcomm processor - the Secure UI component is specific to Qualcomm hardware
-
Confirm CAF build variantCheck if the Android build is a CAF (Code Aurora Forum) variant by examining build properties: run 'getprop ro.build.version.incremental' or check /system/build.prop for CAF-specific build fingerprintsAffected if Build is not a CAF variant - the vulnerability specifically affects CAF versions of Android with Qualcomm Secure UI
-
Verify Secure UI component presenceCheck for the presence of Qualcomm Secure UI-related services or drivers - look for files in /vendor/lib/hw/ or /system/lib/ containing 'secureui' or check dmesg output for Secure UI kernel messagesAffected if Secure UI component is not present on the device - the race condition only exists where this component is loaded
-
Check kernel version and CAF tagRun 'uname -a' and examine the kernel version string. CAF builds typically contain 'caf' or 'msm' in the version. Also check /proc/version for Code Aurora Forum identifiersAffected if Kernel does not show CAF identifiers and is a stock Google/AOSP build - the vulnerability is in the CAF-specific Secure UI implementation
A user is affected if their Android device uses a Qualcomm processor with the Secure UI component AND is running a CAF (Code Aurora Forum) kernel build, as the TOCTOU race condition exists specifically in the CAF implementation of Qualcomm's Secure UI.
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 data应用高通和设备制造商发布的安全补丁;在补丁可用前,可考虑限制对敏感安全UI操作的访问以降低攻击面。
- 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-2016-10383 — 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-2016-10383 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