Home/CVE/Double free issue can happen when sensor power settings is freed by some thread while another thread try to access. in S
CVE
CVE-2019-10565
Double free issue can happen when sensor power settings is freed by some thread while another thread try to access. in S
Double 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.
CRITICAL · CVSS 9.8
EPSS 0.00711
EPSS exploitation odds0.71% · top 50%
Schedule remediation
- CVSS base score ≥ 7.0
No Sigma yet — build one →
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2019-10565, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
↗
Exploitation momentum
1237 days of EPSSdormant
Flat and low - no real exploitation pressure. This reads the direction and speed of EPSS over time, which can move before EPSS itself peaks or before CISA lists it.
EPSS exploitation probability
0.71%
Top 50%odds of exploitation in the next 30 days
CVSS metric silhouette
shape grows toward worst-case
SSVC triage
No SSVC vulnrichment for this CVE. CISA's Vulnrichment program scores newer CVEs (~2024 onwards) plus selected older critical ones. Use the EPSS probability + KEV status to triage instead.
CVSS vector breakdown
Exploitability - how they get in
Attack Vector
Network
Adjacent
Local
Physical
Attack Complexity
Low
High
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Impact - what breaks
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
VECTOR
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HLifecycle
- 06 Nov 2019Published to NVD
- 17 Jun 2026Last modified
Every entry is a recorded date - NVD publish/modify, CISA KEV add, public exploit disclosure. No inferred events.
Attack path
Full kill chain
◆
ATT&CK techniques
1Techniques this CVE enables. Pills with a solid outline are high confidence - named directly in ATT&CK or Nuclei, or human-curated by CTID; the rest are inferred from the weakness type using MITRE's CVE Mapping Methodology and the CWE → CAPEC chain. Broad, generic-weakness guesses are filtered out. A small N× marks a technique that N independent sources agree on.
▤ Build a SIEM detection for these techniques⬡
Weakness Classification
CWE-415Double Free
▤
Affected Products & Versions
13qualcomm apq8053 firmwareall versions
qualcomm mdm9206 firmwareall versions
qualcomm mdm9207c firmwareall versions
qualcomm mdm9607 firmwareall versions
qualcomm msm8905 firmwareall versions
qualcomm msm8909 firmwareall versions
qualcomm msm8909w firmwareall versions
qualcomm qcn7605 firmwareall versions
qualcomm qcs405 firmwareall versions
qualcomm qcs605 firmwareall versions
qualcomm sdm845 firmwareall versions
qualcomm sdx24 firmwareall versions
qualcomm sxr1130 firmwareall versions
▤
Related CVEs
8CVEs linked to this one by a shared weakness (CWE) or affected product - joins on data already in the engine, with the reason shown per row.
CVE-2002-0059
The decompression algorithm in zlib 1.1.3 and earlier, as used in many different...
same CWE-415
CRITICAL
CVE-2003-0015
Double-free vulnerability in CVS 1.11.4 and earlier allows remote attackers to c...
1
same CWE-415
CVE-2003-0545
Double free vulnerability in OpenSSL 0.9.7 allows remote attackers to cause a de...
same CWE-415
CRITICAL
CVE-2003-1048
Double free vulnerability in mshtml.dll for certain versions of Internet Explore...
same CWE-415
HIGH
CVE-2018-13916
Out-of-bounds memory access in Qurt kernel function when using the identifier to...
same product
HIGH
CVE-2018-11980
When a fake broadcast/multicast 11w rmf without mmie received, since no proper l...
same product
HIGH
CVE-2018-11838
Possible double free issue in WLAN due to lack of checking memory free condition...
same product
HIGH
CVE-2018-13903
u'Error in UE due to race condition in EPCO handling' in Snapdragon Auto, Snapdr...
same product
HIGH
🔗
References & Sources
1Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.