CVE-2019-2250
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 · uneditedKernel can write to arbitrary memory address passed by user while freeing/stopping a thread in Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile in QCS605, SD 675, SD 712 / SD 710 / SD 670, SD 835, SD 845 / SD 850, SD 855, SD 8CX, SM7150, SXR1130
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 local privilege escalation vulnerability exists in the Qualcomm kernel where user-supplied memory addresses can be written to during thread freeing/stopping operations. The kernel incorrectly trusts user-provided pointers and writes to arbitrary kernel or user memory locations, potentially allowing a local attacker to corrupt memory and escalate privileges.
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.0/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 Qualcomm SoC modelCheck /proc/cpuinfo or /sys/devices/soc0/ for the chip identifier (e.g., 'sd845', 'sd835', 'qc605')Affected if The SoC matches any of the affected models: Qcs605, Sd 675, Sd 712, Sd 710, Sd 670, Sd 835, Sd 845, or Sd 850
-
Check the kernel versionRun 'uname -r' or check /proc/version to retrieve the running kernel version stringAffected if The kernel version corresponds to the affected firmware versions which are all versions of the listed Qualcomm chipsets (no patch level is safe since all versions are affected)
-
Verify the device is running Qualcomm-based firmwareCheck /sys/firmware/devicetree/base/model or /sys/class/leds for Qualcomm-specific entries, or check the bootloader splash screen and boot logsAffected if The device uses Qualcomm Snapdragon firmware and matches the affected product list
-
Confirm the kernel thread management subsystem is presentCheck for the presence of kernel thread handling code by examining /proc/kallsyms for thread_free, thread_stop, or similar kernel thread management functions referenced in the vulnerabilityAffected if The kernel exposes thread management operations that accept user-supplied pointers without validation
If the device uses any of the listed Qualcomm Snapdragon chipsets (Qcs605, Sd 675, 712, 710, 670, 835, 845, 850) with unpatched firmware, the environment is affected by this privilege escalation 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-specific security patches from the device/OEM manufacturer for affected Snapdragon devices. This is a firmware-level fix requiring kernel updates from Qualcomm and subsequent OEM distribution.
- Consultation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,048.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-2250 — 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-2019-2250 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