CVE-2019-10565
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 · uneditedDouble free issue can happen when sensor power settings is freed by some thread while another thread try to access. in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in APQ8053, MDM9206, MDM9207C, MDM9607, MSM8905, MSM8909, MSM8909W, QCN7605, QCS405, QCS605, SDM845, SDX24, 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 double-free vulnerability exists in the sensor power settings management code of affected Snapdragon chipsets. The issue occurs when one thread frees sensor power settings while another thread simultaneously attempts to access them, creating a race condition that leads to memory corruption.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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 the chipset modelUse commands such as 'cat /proc/cpuinfo', 'dmesg | grep -i qualcomm', or check boot logs to determine the exact Qualcomm chipset model present in the deviceAffected if The chipset matches any of these: Apq8053, Mdm9206, Mdm9207c, Mdm9607, Msm8905, Msm8909, Msm8909w, or Qcn7605
-
Check for sensor subsystem activityInspect running processes or kernel modules related to sensors using 'ps | grep -i sensor' or 'ls /dev/sensor*' to determine if the sensor power management subsystem is activeAffected if Sensor-related processes or device nodes are present and active on the system
-
Review system logs for memory corruption indicatorsExamine kernel logs (dmesg) and system logs (logcat for Android, /var/log/messages for Linux) for signs of double-free errors, memory corruption, or unexpected crashes related to sensor power settingsAffected if Logs contain error messages mentioning double-free, memory corruption, or crashes in sensor power management code
-
Check for race condition crash signaturesSearch logs for patterns indicating thread synchronization failures such as 'use after free', 'double free', or unexpected sensor subsystem crashes occurring during concurrent sensor operationsAffected if The device experiences crashes or error logs showing concurrent access issues involving sensor power settings
The device is affected if it uses any of the listed Qualcomm chipset models (Apq8053, Mdm9206, Mdm9207c, Mdm9607, Msm8905, Msm8909, Msm8909w, or Qcn7605) and has the sensor power management subsystem active, since all firmware versions for these chipsets contain the vulnerable code.
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 dataImplement proper mutex or lock synchronization around all sensor power settings access and free operations to prevent concurrent access. Review all sensor-related code paths for similar race conditions.
- Consultation6.0 h
- Implementation12.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10565 — 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-10565 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