CVE-2015-9222: In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile and Snapdragon Wear MSM8909W, SD 210/SD 212/SD…
Noroxi assessment
Priority: Monitor (action score 31/100)
- Public proof-of-concept code exists (Exploit-DB); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 4.2% (FIRST EPSS); higher than 91.2% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile and Snapdragon Wear MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 450, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820, SD 835, SD 845, SDM630, SDM636, SDM660, and Snapdragon_High_Med_2016, processing erroneous bitstreams may result in a HW freeze. FW should detect the HW freeze based on watchdog timer, but because the watchdog timer is not enabled, an infinite loop occurs, resulting in a device freeze.
- Published
- Apr 18, 2018
- Updated
- Jun 16, 2026
- EPSS
- 4.2% · 91th percentile
- CWE
- CWE-399
Report tools
Action score
31
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| qualcomm | msm8909w firmware | cpe:2.3:o:qualcomm:msm8909w_firmware |
| qualcomm | msm8909w | cpe:2.3:h:qualcomm:msm8909w |
| qualcomm | sd 210 firmware | cpe:2.3:o:qualcomm:sd_210_firmware |
| qualcomm | sd 210 | cpe:2.3:h:qualcomm:sd_210 |
| qualcomm | sd 212 firmware | cpe:2.3:o:qualcomm:sd_212_firmware |
| qualcomm | sd 212 | cpe:2.3:h:qualcomm:sd_212 |
| qualcomm | sd 205 firmware | cpe:2.3:o:qualcomm:sd_205_firmware |
| qualcomm | sd 205 | cpe:2.3:h:qualcomm:sd_205 |
| qualcomm | sd 400 firmware | cpe:2.3:o:qualcomm:sd_400_firmware |
| qualcomm | sd 400 | cpe:2.3:h:qualcomm:sd_400 |
| qualcomm | sd 410 firmware | cpe:2.3:o:qualcomm:sd_410_firmware |
| qualcomm | sd 410 | cpe:2.3:h:qualcomm:sd_410 |
and 36 more
Versions reported by the vendor
Affected version ranges reported by the assigning authority (qualcomm). Independent of NVD's CPE analysis and usually ahead of it.
Qualcomm, Inc. Snapdragon Mobile, Snapdragon Wear
- MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 450, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820, SD 835, SD 845, SDM630, SDM636, SDM660, Snapdragon_High_Meaffected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- qualcomm msm8909w firmwareall versions
- qualcomm sd 205 firmwareall versions
- qualcomm sd 210 firmwareall versions
- qualcomm sd 212 firmwareall versions
- qualcomm sd 400 firmwareall versions
- qualcomm sd 410 firmwareall versions
- qualcomm sd 412 firmwareall versions
- qualcomm sd 425 firmwareall versions
- qualcomm sd 427 firmwareall versions
- qualcomm sd 430 firmwareall versions
- qualcomm sd 435 firmwareall versions
- qualcomm sd 450 firmwareall versions
- qualcomm sd 625 firmwareall versions
- qualcomm sd 650 firmwareall versions
- qualcomm sd 652 firmwareall versions
- qualcomm sd 800 firmwareall versions
- qualcomm sd 808 firmwareall versions
- qualcomm sd 810 firmwareall versions
- qualcomm sd 820 firmwareall versions
- qualcomm sd 835 firmwareall versions
Same product
qualcomm: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-11076Use of Out-of-range Pointer Offset in Video39Monitor
- CVE-2019-2285Out of bound write issue is observed while giving information about properties that have been set so far for playing video in Snapdragon…39Monitor
- CVE-2019-10538Lack of check of address range received from firmware response allows modem to respond arbitrary pages into its address range which can…39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2015-9217Apr 18, 2018 · In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile and Snapdragon Wear MSM8909W, SD 210/SD 212/SD…31Monitor
- ← EarlierCVE-2015-9218Apr 18, 2018 · In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile and Snapdragon Wear MSM8909W, SD 210/SD 212/SD…22Monitor
- Later →CVE-2017-11088Jul 6, 2018 · Improper Input Validation in Linux io-prefetch in Snapdragon Mobile and Snapdragon Wear, A SQL injection vulnerability exists in versions…39Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Exploit-DB entry ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | webapps | 2016-04-27 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- First PoC-721 d
- Published
- TodayNov 16, 2026+3134 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-399 · Resource Management ErrorsCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.