CVE-2019-10582
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 issue due to using of invalidated iterator to delete an object in sensors HAL in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in APQ8096AU, MSM8909W, Nicobar, QCS605, SA6155P, SDA845, SDM429W, SDM670, SDM710, SDM845, SM6150, SM8150, SM8250, SXR1130, SXR2130
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 confidenceUse-after-free vulnerability in the sensors HAL (Hardware Abstraction Layer) where an invalidated iterator is used to delete an object, leading to memory corruption. This occurs when the iterator's validity is not checked before performing the delete operation, allowing a freed memory location to be accessed.
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 the Qualcomm chipset modelCheck the processor/soc model on the device (e.g., via /proc/cpuinfo, or system information settings on Android)Affected if The chipset model matches one of: Apq8096au, Mdm9607, Msm8909w, Nicobar, Qcs605, Sa6155p, Sda845, or Sdm429w
-
Confirm sensors HAL is in useCheck if the sensors hardware abstraction layer is active on the device (on Android, look for sensors.* service in dumpsys, or check /vendor/etc/vintf/manifest.xml for hal/sensors)Affected if The sensors HAL is loaded and functional on the device
-
Verify firmware versionObtain the firmware/baseband version string (on Android: Settings > About Phone > Build Number, or via AT command on modem, or /sys/firmware_version)Affected if The firmware is from the affected Qualcomm product lines (all versions of the listed chipsets are affected)
-
Check for sensor service instabilityMonitor sensors service ([email protected] service) for crashes or anomalous behavior using logcat | grep sensors or bugreport analysisAffected if Sensors service exhibits unexpected crashes or memory corruption errors related to iterator operations
The device is affected if it uses any of the listed Qualcomm chipsets (Apq8096au, Mdm9607, Msm8909w, Nicobar, Qcs605, Sa6155p, Sda845, or Sdm429w) with an active sensors HAL, as all firmware versions of these products contain the 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 the Qualcomm-provided security patch for the affected chipsets. The fix requires correcting the iterator lifecycle management in the sensors HAL code to ensure iterators are validated before use.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10582 — 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-10582 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