| CVE-2015-9148US | critical9.8 | 1.34% (71st) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9625, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, SD 400, SD 425, SD 430, SD 450, SD 600, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820, SD 820A, SD 835, SD 845, SD 850, SDX20 |
| CVE-2016-10426US | critical9.8 | 1.28% (70th) | — | ✗kein Fix | 2018-04-18 | ≤ SD 410/12, SD 425, SD 430, SD 450, SD 617, SD 625, SD 650/52, SD 810, SD 820, SD 820A |
| CVE-2015-9111US | critical9.8 | 1.27% (70th) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9625, SD 425, SD 430, SD 450, SD 625, SD 650/52, SD 820, SD 820A |
| CVE-2017-18318US | critical9.8 | 1.27% (70th) | — | ✗kein Fix | 2018-11-28 | ≤ MSM8996AU, SD 410/12, SD 425, SD 430, SD 450, SD 625, SD 650/52, SD 810, SD 820, SD 820A |
| CVE-2015-9112US | critical9.8 | 1.27% (70th) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9625, SD 400, SD 800, SD 820, SD 820A |
| CVE-2017-18132US | critical9.8 | 1.25% (69th) | — | ✗kein Fix | 2018-04-11 | ≤ MDM9206, MDM9607, MDM8996 |
| CVE-2017-18129US | critical9.8 | 1.25% (69th) | — | ✗kein Fix | 2018-04-11 | ≤ MDM9206, MDM9607, SD 845, MSM8996, MSM8998 |
| CVE-2015-9116US | critical9.8 | 1.25% (69th) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9625, SD 425, SD 430, SD 450, SD 625, SD 650/52, SD 810, SD 820, SD 820A |
| CVE-2015-9114US | critical9.8 | 1.25% (69th) | — | ✗kein Fix | 2018-04-18 | ≤ SD 425, SD 430, SD 450, SD 625, SD 650/52, SD 820, SD 820A |
| CVE-2015-9110US | critical9.8 | 1.25% (69th) | — | ✗kein Fix | 2018-04-18 | ≤ SD 425, SD 430, SD 450, SD 625, SD 650/52, SD 820, SD 820A |
| CVE-2015-9109US | critical9.8 | 1.25% (69th) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9625, SD 425, SD 430, SD 450, SD 625, SD 650/52, SD 820, SD 820A |
| CVE-2016-10486US | critical9.8 | 1.19% (68th) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9640, MDM9645, SD 210/SD 212/SD 205, SD 450, SD 617, SD 625, SD 650/52, SD 808, SD 810, SD 820, SD 820A |
| CVE-2016-10471US | critical9.8 | 1.19% (68th) | — | ✗kein Fix | 2018-04-18 | ≤ SD 425, SD 430, SD 450, SD 625, SD 650/52, SD 820, SD 820A |
| CVE-2016-10467US | critical9.8 | 1.19% (68th) | — | ✗kein Fix | 2018-04-18 | ≤ 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 820, SD 820A |
| CVE-2016-10452US | critical9.8 | 1.19% (68th) | — | ✗kein Fix | 2018-04-18 | ≤ 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 820A, SD 835 |
| CVE-2016-10445US | critical9.8 | 1.19% (68th) | — | ✗kein Fix | 2018-04-18 | ≤ SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 450, SD 615/16/SD 415, SD 625, SD 820, SD 820A, SD 835, SD 845, SD 850, SDM630, SDM636, SDM660, Snapdragon_High_Med_2016 |
| CVE-2015-9199US | critical9.8 | 1.19% (68th) | — | ✗kein Fix | 2018-04-18 | ≤ IPQ4019, MDM9625, MDM9635M, MDM9640, MDM9650, MDM9655, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 615/16/SD 415, SD 800, SD 808, SD 810, SD 820, SD 820A |
| CVE-2015-9167US | critical9.8 | 1.19% (68th) | — | ✗kein Fix | 2018-04-18 | ≤ 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 820A |
| CVE-2015-9108US | critical9.8 | 1.16% (67th) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9625, SD 425, SD 430, SD 450, SD 625, SD 650/52, SD 820, SD 820A |
| CVE-2015-9115US | critical9.8 | 1.15% (67th) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9625, SD 410/12, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 820, SD 820A |
| CVE-2015-9113US | critical9.8 | 1.15% (67th) | — | ✗kein Fix | 2018-04-18 | ≤ MDM9625, SD 425, SD 430, SD 450, SD 625, SD 650/52, SD 810, SD 820, SD 820A |
| CVE-2016-10462US | critical9.8 | 1.12% (66th) | — | ✗kein Fix | 2018-04-18 | ≤ SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 450, SD 615/16/SD 415, SD 625, SD 650/52, SD 808, SD 810, SD 820, SD 820A, SD 835, SDM630, SDM636, SDM660, Snapdragon_High_Med_2016 |
| CVE-2015-9152US | critical9.8 | 1.12% (66th) | — | ✗kein Fix | 2018-04-18 | ≤ IPQ4019, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 450, SD 615/16/SD 415, SD 625, SD 800, SD 810, SD 820, SD 820A, SD 835, Snapdragon_High_Med_2016 |
| CVE-2016-10430US | critical9.8 | 0.95% (61st) | — | ✗kein Fix | 2018-04-18 | ≤ SD 425, SD 430, SD 450, SD 625, SD 650/52, SD 820, SD 820A |
| CVE-2016-10428US | high7.5 | 0.84% (58th) | — | ✗kein Fix | 2018-04-18 | ≤ SD 425, SD 430, SD 450, SD 625, SD 650/52, SD 820, SD 820A |
| CVE-2016-10423US | high7.5 | 0.84% (58th) | — | ✗kein Fix | 2018-04-18 | ≤ SD 425, SD 430, SD 450, SD 625, SD 650/52, SD 820, SD 820A |
| CVE-2016-10434US | high7.5 | 0.80% (56th) | — | ✗kein Fix | 2018-04-18 | ≤ SD 820, SD 820A |
| CVE-2016-10439US | high8.1 | 0.76% (55th) | — | ✗kein Fix | 2018-04-18 | ≤ SD 425, SD 430, SD 450, SD 625, SD 650/52, SD 820, SD 820A |
| CVE-2016-10432US | high8.1 | 0.76% (55th) | — | ✗kein Fix | 2018-04-18 | ≤ SD 410/12, SD 425, SD 430, SD 450, SD 617, SD 625, SD 650/52, SD 820, SD 820A |
| CVE-2016-10409US | high8.1 | 0.76% (55th) | — | ✗kein Fix | 2018-04-18 | ≤ SD 425, SD 430, SD 450, SD 625, SD 650/52, SD 820, SD 820A, SD 835 |
| CVE-2018-5868US | high7.8 | 0.26% (18th) | — | ✗kein Fix | 2019-01-18 | ≤ MSM8996AU, SD 425, SD 430, SD 450, SD 625, SD 712 / SD 710 / SD 670, SD 820, SD 820A, SD 835, SD 845 / SD 850, SDA660, SDX24, SXR1130 |
| CVE-2018-5917US | high7.8 | 0.26% (18th) | — | ✗kein Fix | 2018-11-28 | ≤ MSM8996AU, SD 425, SD 430, SD 450, SD 625, SD 820, SD 820A, SD 835, SD 845, SD 850, SDA660, SDA845, SDX24, SXR1130 |
| CVE-2018-5912US | high7.8 | 0.23% (13th) | — | ✗kein Fix | 2018-11-28 | ≤ MSM8996AU, SD 450, SD 625, SD 820, SD 820A, SD 835, SD 845, SD 850, SDA660 |
| CVE-2017-18155US | high7.8 | 0.23% (13th) | — | ✗kein Fix | 2018-07-12 | ≤ MSM8996AU, SD 450, SD 625, SD 820, SD 820A, SD 835 |
| CVE-2017-18317US | high7.8 | 0.22% (13th) | — | ✗kein Fix | 2018-11-28 | ≤ MSM8996AU,SD 410/12,SD 820,SD 820A |
| CVE-2017-18320US | high7.8 | 0.22% (13th) | — | ✗kein Fix | 2019-01-03 | ≤ MSM8996AU, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 615/16/SD 415, SD 625, SD 632, SD 636, SD 650/52, SD 712 / SD 710 / SD 670, SD 810, SD 820, SD 820A, SD 835, SDA660, SDM439, SDM630, SDM660, SDX24, Snapdragon_High_Med_2016, SXR1130 |
| CVE-2017-18172US | high7.8 | 0.21% (11th) | — | ✗kein Fix | 2018-10-23 | ≤ MDM9635M, SD 400, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 800, SD 810, SD 820, SD 820A, SD 835, SDM630, SDM636, SDM660, Snapdragon_High_Med_2016 |
| CVE-2017-18312US | high7.8OT erhöht | 0.18% (8th) | — | ✗kein Fix | 2018-10-23 | ≤ MSM8996AU, SD 410/12, SD 617, SD 650/52, SD 810, SD 820, SD 820A |
| CVE-2017-18302US | medium4.7 | 0.17% (7th) | — | ✗kein Fix | 2018-09-20 | ≤ MSM8996AU, SD 425, SD 427, SD 430, SD 435, SD 450, SD 625, SD 650/52, SD 820, SD 820A, SD 835, SDA660, SDM429, SDM439, SDM630, SDM632, SDM636, SDM660, Snapdragon_High_Med_2016 |