| CVE-2022-22077US | high7.8 | 0.14% (4th) | Exploit | ✗no fix | 2022-10-19 | ≤ SD 8 Gen1 5G, WCD9380, WCN6855, WCN6856, WCN7850, WCN7851, WSA8830, WSA8835 |
| CVE-2017-14915US | critical9.8 | 1.62% (76th) | — | ✗no fix | 2018-03-30 | ≤ SD 625, SD 650/52, SD 835 |
| CVE-2015-9219US | critical9.8 | 1.42% (73rd) | — | ✗no fix | 2018-04-18 | ≤ SD 400, SD 800 |
| CVE-2015-9150US | critical9.8 | 1.42% (73rd) | — | ✗no fix | 2018-04-18 | ≤ MDM9625, MDM9635M, SD 400, SD 800 |
| CVE-2016-10496US | critical9.8 | 1.38% (72nd) | — | ✗no fix | 2018-04-18 | ≤ MDM9635M, SD 210/SD 212/SD 205, SD 410/12, SD 450, SD 615/16/SD 415, SD 625, SD 650/52, SD 808, SD 810 |
| CVE-2015-9215US | critical9.8 | 1.38% (72nd) | — | ✗no fix | 2018-04-18 | ≤ MDM9615, MDM9625, MDM9635M, SD 810 |
| CVE-2015-9223US | critical9.8 | 1.35% (71st) | — | ✗no fix | 2018-04-18 | ≤ MDM9615, MDM9625, MDM9635M, SD 400, SD 600, SD 800 |
| CVE-2015-9179US | critical9.8 | 1.35% (71st) | — | ✗no fix | 2018-04-18 | ≤ MSM8974 |
| CVE-2016-10478US | critical9.8 | 1.34% (71st) | — | ✗no fix | 2018-04-18 | ≤ SD 617 |
| CVE-2016-10475US | critical9.8 | 1.34% (71st) | — | ✗no fix | 2018-04-18 | ≤ SD 210/SD 212/SD 205, SD 400, SD 430, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820 |
| CVE-2016-10407US | critical9.8 | 1.34% (71st) | — | ✗no fix | 2018-04-18 | ≤ SD 210/SD 212/SD 205, SD 400, SD 410/12, 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-2014-9994US | critical9.8 | 1.34% (71st) | — | ✗no fix | 2018-04-18 | ≤ SD 400, SD 800 |
| CVE-2016-10458US | critical9.8 | 1.33% (71st) | — | ✗no fix | 2018-04-18 | ≤ SD 210/SD 212/SD 205, 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 808, SD 810, SD 820, SD 835, SD 845, SDM630, SDM636, SDM660, SDX20, Snapdragon_High_Med_2016 |
| CVE-2015-9118US | critical9.8 | 1.33% (71st) | — | ✗no fix | 2018-04-18 | ≤ MDM9615, MDM9625, MDM9635M, SD 400, SD 410/12, SD 615/16/SD 415, SD 800, SD 808, SD 810 |
| CVE-2015-9133US | critical9.8 | 1.31% (71st) | — | ✗no fix | 2018-04-18 | ≤ SD 400, SD 410/12, SD 617, SD 650/52, SD 800, SD 810 |
| CVE-2016-10477US | critical9.8 | 1.28% (70th) | — | ✗no fix | 2018-04-18 | ≤ SD 210/SD 212/SD 205, SD 400, SD 430, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820 |
| CVE-2015-9195US | critical9.8 | 1.28% (70th) | — | ✗no fix | 2018-04-18 | ≤ MDM9625, MDM9635M, MDM9650, MDM9655, SD 400, SD 410/12, SD 615/16/SD 415, SD 617, SD 650/52, SD 808, SD 810, SDX20 |
| CVE-2014-9996US | critical9.8 | 1.28% (70th) | — | ✗no fix | 2018-04-18 | ≤ SD 400, SD 800 |
| CVE-2014-9995US | critical9.8 | 1.28% (70th) | — | ✗no fix | 2018-04-18 | ≤ SD 400, SD 800 |
| CVE-2014-10056US | critical9.8 | 1.28% (70th) | — | ✗no fix | 2018-04-18 | ≤ SD 210/SD 212/SD 205 |
| CVE-2018-3589US | critical9.8 | 1.28% (70th) | — | ✗no fix | 2018-04-11 | ≤ MDM9650, MDM9655, SD 835, SD 845, SD 850 |
| CVE-2017-18142US | critical9.8 | 1.28% (70th) | — | ✗no fix | 2018-04-11 | ≤ MDM9650, MDM9655, SD 835, SD 845, SD 850 |
| CVE-2017-18137US | critical9.8 | 1.28% (70th) | — | ✗no fix | 2018-04-11 | ≤ MDM9640, MDM9645, MDM9650, MDM9655, SD 450, SD 625, SD 650/52, SD 810, SD 820, SD 835 |
| CVE-2017-18135US | critical9.8 | 1.28% (70th) | — | ✗no fix | 2018-04-11 | ≤ MDM9650, MDM9655, SD 450, SD 625, SD 650/52, SD 835, SD 845, SD 850 |
| CVE-2017-18134US | critical9.8 | 1.28% (70th) | — | ✗no fix | 2018-04-11 | ≤ SD 845, SD 850 |
| CVE-2015-9151US | critical9.8 | 1.28% (70th) | — | ✗no fix | 2018-04-18 | ≤ MDM9625, MDM9635M, SD 400, SD 800 |
| CVE-2015-9147US | critical9.8 | 1.28% (70th) | — | ✗no fix | 2018-04-18 | ≤ MDM9625, MDM9635M, SD 400, SD 800 |
| CVE-2015-9221US | critical9.8 | 1.25% (69th) | — | ✗no fix | 2018-04-18 | ≤ SD 400, SD 800, SD 810 |
| CVE-2015-9174US | critical9.8 | 1.25% (69th) | — | ✗no fix | 2018-04-18 | ≤ SD 410/12, SD 617, SD 650/52, SD 800, SD 808, SD 810 |
| CVE-2017-8275US | critical9.8 | 1.24% (69th) | — | ✗no fix | 2018-04-11 | ≤ SD 210/SD 212/SD 205, SD 400, SD 430, SD 450, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 820, SD 835 |
| CVE-2016-10498US | critical9.8 | 1.23% (69th) | — | ✗no fix | 2018-04-18 | ≤ MDM9635M, MDM9645, MDM9650, MDM9655, 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 617, SD 625, SD 650/52, SD 810, SDM630, SDM636, SDM660, Snapdragon_High_Med_2016 |
| CVE-2014-9985US | critical9.8 | 1.19% (68th) | — | ✗no fix | 2018-04-18 | ≤ MDM9635M, SD 400, SD 800 |
| CVE-2016-10495US | critical9.8 | 1.19% (68th) | — | ✗no fix | 2018-04-18 | ≤ MDM9635M |
| CVE-2016-10489US | critical9.8 | 1.19% (68th) | — | ✗no fix | 2018-04-18 | ≤ SD 400 |
| CVE-2016-10479US | critical9.8 | 1.19% (68th) | — | ✗no fix | 2018-04-18 | ≤ MDM9607, MDM9615, MDM9635M, MDM9640, SD 210/SD 212/SD 205, SD 400, SD 600, SD 615/16/SD 415, SD 617, SD 650/52, SD 800, SD 810, SD 820 |
| CVE-2016-10461US | critical9.8 | 1.19% (68th) | — | ✗no fix | 2018-04-18 | ≤ MDM9650, SD 650/52, SD 808, SD 810, SD 820, SDX20 |
| CVE-2016-10460US | critical9.8 | 1.19% (68th) | — | ✗no fix | 2018-04-18 | ≤ SD 835, SD 845, SD 850 |
| CVE-2016-10454US | critical9.8 | 1.19% (68th) | — | ✗no fix | 2018-04-18 | ≤ SD 425, SD 430, SD 450, SD 625 |
| CVE-2016-10419US | critical9.8 | 1.19% (68th) | — | ✗no fix | 2018-04-18 | ≤ MDM9640, MDM9645, MDM9650, MDM9655, SD 450, SD 625, SD 650/52, SD 820, SD 835, SD 845, SD 850, SDX20 |
| CVE-2015-9146US | critical9.8 | 1.19% (68th) | — | ✗no fix | 2018-04-18 | ≤ MDM9625, MDM9635M, MDM9645, MDM9650, MDM9655, SD 400, SD 800, SD 835, SD 845, SD 850, SDX20 |
| CVE-2015-9142US | critical9.8 | 1.19% (68th) | — | ✗no fix | 2018-04-18 | ≤ MDM9645, MDM9650, 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 650/52, SD 800, SD 808, SD 810, SD 820, SDM630, SDM636, SDM660, Snapdragon_High_Med_2016 |
| CVE-2014-10057US | critical9.8 | 1.19% (68th) | — | ✗no fix | 2018-04-18 | ≤ MDM9615, MDM9625, MDM9635M, MDM9640, MDM9650, SD 210/SD 212/SD 205, SD 400, SD 425, SD 430, SD 435, SD 617, SD 625, Snapdragon_High_Med_2016 |
| CVE-2014-10046US | critical9.8 | 1.19% (68th) | — | ✗no fix | 2018-04-18 | ≤ MDM9615, MDM9625, MDM9635M, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 615/16/SD 415, SD 800, SD 808, SD 810 |
| CVE-2014-10039US | critical9.8 | 1.19% (68th) | — | ✗no fix | 2018-04-18 | ≤ MDM9625, SD 400, SD 800 |
| CVE-2015-9173US | critical9.8 | 1.16% (67th) | — | ✗no fix | 2018-04-18 | ≤ SD 410/12, SD 617, SD 650/52, SD 800, SD 808, SD 810 |
| CVE-2015-9066US | critical9.8 | 1.13% (66th) | — | ✗no fix | 2017-08-18 | ≤ MDM9615 |
| CVE-2015-9063US | critical9.8 | 1.13% (66th) | — | ✗no fix | 2017-08-18 | ≤ MDM9640, MDM9645, SD 450, SD 617, SD 625, SD 650/52, SD 820 |
| CVE-2016-10442US | critical9.8 | 1.12% (66th) | — | ✗no fix | 2018-04-18 | ≤ MDM9640, SDM630, MSM8976, MSM8937, SDM845, MSM8976, MSM8952 |
| CVE-2016-10440US | critical9.8 | 1.12% (66th) | — | ✗no fix | 2018-04-18 | ≤ SD 425, SD 430, SD 450, SD 625, SD 650/52 |
| CVE-2014-10059US | critical9.8 | 1.12% (66th) | — | ✗no fix | 2018-04-18 | ≤ MDM9615,MDM9625,SD 210/SD 212/SD 205,SD 400,SD 800 |