| CVE-2015-9222US | high7.5 | 4.27% (91st) | Exploit | ✗kein Fix | 2018-04-18 | ≤ 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_Med_2016 |
| CVE-2016-10502US | critical9.8 | 1.46% (73rd) | — | ✗kein Fix | 2018-12-10 | ≤ MDM9206, MDM9607, MDM9650, SD 210/SD 212/SD 205, SD 835, SDA660 |
| CVE-2015-9122US | critical9.8 | 1.38% (72nd) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9206, MDM9607, MDM9635M, MDM9640, MDM9645, MDM9655, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820, SD 835 |
| CVE-2016-10449US | critical9.8 | 1.38% (72nd) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9206, MDM9607, MDM9640, MDM9650, MSM8909W, SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 625, SD 650/52, SD 800, SD 810, SD 820, SD 835 |
| CVE-2016-10491US | critical9.8 | 1.34% (71st) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9206, MDM9607, MDM9625, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820, SD 835, SD 845, SD 850, SDX20, , , , , |
| CVE-2016-10485US | critical9.8 | 1.28% (70th) | — | ✗kein Fix | 2018-04-18 | ≤ IPQ4019, MDM9206, MDM9607, MDM9625, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 615/16/SD 415, SD 617, SD 650/52, SD 800, SD 808, SD 810, SDX20 |
| CVE-2016-10473US | critical9.8 | 1.28% (70th) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9206, MDM9607, MDM9650, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 450, SD 600, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820, SD 835, SDX20 |
| CVE-2016-10441US | critical9.8 | 1.28% (70th) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9206, MDM9607, MDM9650, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 450, SD 600, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820, SD 835, SDX20 |
| CVE-2016-10410US | critical9.8 | 1.28% (70th) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9206, MDM9607, MDM9615, MDM9625, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820, SD 835, SD 845, SD 850, SDX20 |
| CVE-2015-9161US | critical9.8 | 1.28% (70th) | — | ✗kein Fix | 2018-04-18 | ≤ MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 615/16/SD 415, SD 617, SD 650/52, SD 800, SD 808, SD 810 |
| CVE-2015-9156US | critical9.8 | 1.28% (70th) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9206, MDM9607, MDM9635M, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 615/16/SD 415, SD 617, SD 800, SD 808, SD 810 |
| CVE-2015-9144US | critical9.8 | 1.28% (70th) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9206, MDM9607, MDM9615, MDM9625, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820, SD 835, SD 845, SD 850, SDX20 |
| CVE-2015-9143US | critical9.8 | 1.28% (70th) | — | ✗kein Fix | 2018-04-18 | ≤ IPQ4019, MDM9206, MDM9607, MDM9615, MDM9625, MDM9640, MDM9650, MDM9655, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 600, SD 615/16/SD 415, SDX20 |
| CVE-2015-9136US | critical9.8 | 1.28% (70th) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9206, MDM9607, MDM9640, MDM9650, SD 210/SD 212/SD 205, SD 425, SD 430, SD 450, SD 600, SD 625, SD 650/52, SD 808, SD 810, SD 820, SD 835, SDX20 |
| CVE-2014-9991US | critical9.8 | 1.28% (70th) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9206, MDM9625, MDM9635M, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 615/16/SD 415, SD 625, SD 650/52, SD 808, SD 810, SD 450 |
| CVE-2014-10045US | critical9.8 | 1.28% (70th) | — | ✗kein Fix | 2018-04-18 | ≤ IPQ4019, MDM9206, MDM9607, MDM9615, MDM9625, MDM9635M, MDM9640, MDM9650, MDM9655, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 615/16/SD 415, SD 820, SDX20 |
| CVE-2017-18139US | critical9.8 | 1.28% (70th) | — | ✗kein Fix | 2018-04-11 | ≤ MDM9206, MDM9607, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 808, SD 810, SD 820, SD 835, SD 845, SD 850 |
| CVE-2017-18138US | critical9.8 | 1.28% (70th) | — | ✗kein Fix | 2018-04-11 | ≤ MDM9206, MDM9607, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 808, SD 810, SD 820, SD 835, SD 845, SD 850 |
| CVE-2017-18127US | critical9.8 | 1.28% (70th) | — | ✗kein Fix | 2018-04-11 | ≤ MSM8909W, SD 210/SD 212/SD 205, SD 430, SD 450, SD 625, SD 650/52, SD 820, SD 835, SD 845 |
| CVE-2017-18160US | critical9.8 | 1.27% (70th) | — | ✗kein Fix | 2019-01-18 | ≤ MDM9635M, MDM9645, MDM9650, MDM9655, MSM8909W, SD 835, SD 845, SD 850 |
| CVE-2015-8593US | critical9.8 | 1.27% (70th) | — | ✗kein Fix | 2017-08-18 | ≤ MDM9607, MDM9635M, MSM8909W, SD 210/SD 212/SD 205, SD 425, SD 430 |
| CVE-2015-9126US | critical9.8 | 1.27% (70th) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9607, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8909W, SD 210/SD 212/SD 205, SD 425, SD 430, SD 450, SD 617, SD 625, SD 650/52, SD 808, SD 810, SD 820, SD 835, SD 845, SD 850, SDX20 |
| CVE-2015-9130US | critical9.8 | 1.26% (69th) | — | ✗kein Fix | 2018-04-18 | ≤ MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 615/16/SD 415, SD 617, SD 650/52, SD 808, SD 810 |
| CVE-2015-9127US | critical9.8 | 1.26% (69th) | — | ✗kein Fix | 2018-04-18 | ≤ MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 615/16/SD 415, SD 810 |
| CVE-2015-9212US | critical9.8 | 1.25% (69th) | — | ✗kein Fix | 2018-04-18 | ≤ MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 800 |
| CVE-2015-9205US | critical9.8 | 1.25% (69th) | — | ✗kein Fix | 2018-04-18 | ≤ MSM8909W, SD 210/SD 212/SD 205, SD 410/12, SD 615/16/SD 415, SD 808, SD 810 |
| CVE-2015-9204US | critical9.8 | 1.25% (69th) | — | ✗kein Fix | 2018-04-18 | ≤ MSM8909W, SD 210/SD 212/SD 205, SD 410/12, SD 615/16/SD 415, SD 808, SD 810 |
| CVE-2015-9220US | critical9.8 | 1.24% (69th) | — | ✗kein Fix | 2018-04-18 | ≤ IPQ4019, IPQ8064, MDM9206, MDM9607, MDM9640, MDM9650, QCA4531, QCA6174A, QCA6574AU, QCA6584, QCA6584AU, QCA9377, QCA9378, QCA9379, QCA9558, QCA9880, QCA9886, QCA9980, SD 210/SD 212/SD 205, SD 425, SD 625, SD 810, SD 820, SDX20 |
| CVE-2015-9141US | critical9.8 | 1.24% (69th) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9206, MDM9607, MDM9635M, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 615/16/SD 415, SD 617, SD 800, SD 808, SD 810 |
| CVE-2015-9190US | critical9.8 | 1.21% (68th) | — | ✗kein Fix | 2018-04-18 | ≤ IPQ4019, MDM9206, MDM9607, MDM9615, MDM9625, MDM9635M, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 600, SD 615/16/SD 415, SD 808, SD 810 |
| CVE-2016-10480US | critical9.8 | 1.20% (68th) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9206, MDM9607, MDM9650, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820, SD 835, SDX20 |
| CVE-2017-18071US | critical9.8 | 1.19% (68th) | — | ✗kein Fix | 2018-04-11 | ≤ MDM9206, MDM9607, MSM8909W, SD 210/SD 212/SD 205, SD 425, SD 430, SD 450, SD 625, SD 650/52 |
| CVE-2016-10482US | critical9.8 | 1.19% (68th) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9206, MDM9607, MDM9625, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820, SD 835, SD 845, SD 850, SDX20 |
| CVE-2016-10481US | critical9.8 | 1.19% (68th) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9206, MDM9607, MDM9635M, MDM9640, MDM9650, QCA4531, QCA6174A, QCA6574AU, QCA6584, QCA6584AU, QCA9377, QCA9378, QCA9379, SD 210/SD 212/SD 205, SD 425, SD 600, SD 625, SD 650/52, SD 808, SD 810, SD 820, SD 835, SD 845, SD 850, SDX20 |
| CVE-2016-10476US | critical9.8 | 1.19% (68th) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9206, MDM9607, MDM9650, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820, SD 835, SDX20 |
| CVE-2016-10466US | critical9.8 | 1.19% (68th) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9206, MDM9607, MDM9625, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820, SD 835, SD 845, SD 850, SDX20 |
| CVE-2016-10457US | critical9.8 | 1.19% (68th) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9206, MDM9607, MDM9650, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820, SD 835, SDX20 |
| CVE-2016-10421US | critical9.8 | 1.19% (68th) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9206, MDM9607, MDM9615, MDM9625, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820, SD 835, SD 845, SD 850, SDX20 |
| CVE-2015-9216US | critical9.8 | 1.19% (68th) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9206, MDM9607, MDM9625, MDM9635M, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 625, SD 650/52, SD 808, SD 810 |
| CVE-2015-9208US | critical9.8 | 1.19% (68th) | — | ✗kein Fix | 2018-04-18 | ≤ IPQ4019, MDM9206, MDM9607, MDM9635M, MDM9640, MDM9645, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 615/16/SD 415, SD 800, SD 810 |
| CVE-2015-9207US | critical9.8 | 1.19% (68th) | — | ✗kein Fix | 2018-04-18 | ≤ MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 615/16/SD 415, SD 617, SD 650/52, SD 800, SD 808, SD 810 |
| CVE-2015-9206US | critical9.8 | 1.19% (68th) | — | ✗kein Fix | 2018-04-18 | ≤ MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 615/16/SD 415, SD 617, SD 650/52, SD 808, SD 810 |
| CVE-2015-9200US | critical9.8 | 1.19% (68th) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9206, MDM9650, SD 210/SD 212/SD 205, SD 425, SD 430, SD 450, SD 625, SD 650/52, SD 835 |
| CVE-2015-9197US | critical9.8 | 1.19% (68th) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9206, MDM9607, MDM9635M, MDM9640, MDM9645, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 615/16/SD 415, SD 617, SD 650/52, SD 808, SD 810 |
| CVE-2015-9191US | critical9.8 | 1.19% (68th) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9206, MDM9607, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 617, SD 650/52, SD 808, SD 810, SDX20 |
| CVE-2015-9165US | critical9.8 | 1.19% (68th) | — | ✗kein Fix | 2018-04-18 | ≤ IPQ4019, MDM9206, MDM9607, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 615/16/SD 415, SD 617, SD 650/52, SD 808, SD 810 |
| CVE-2015-9139US | critical9.8 | 1.19% (68th) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9206, MDM9607, MDM9615, MDM9625, MDM9635M, MDM9640, MDM9645, MDM9655, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 615/16/SD 415, SD 617, SD 650/52, SD 800, SD 808, SD 810, SD 820 |
| CVE-2015-9135US | critical9.8 | 1.19% (68th) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9625, MDM9635M, MDM9640, MDM9645, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 615/16/SD 415, SD 617, SD 650/52, SD 800, SD 808, SD 810 |
| CVE-2014-9990US | critical9.8 | 1.19% (68th) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9206, MDM9607, MDM9615, MDM9625, MDM9635M, MSM8909W, SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 430, SD 600, SD 615/16/SD 415, SD 625, SD 650/52, SD 808, SD 810, SD 450 |
| CVE-2014-9989US | critical9.8 | 1.19% (68th) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9206, MDM9607, MDM9615, MDM9625, MDM9635M, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 600, SD 615/16/SD 415, SD 625, SD 650/52, SD 808, SD 810, SD 450 |