Chipset
Qualcomm MSM8960
Statistics
Released (est):
January 2012
13 years ago
Vulnerabilities:
11
Devices:
30
Vulnerabilities
| Id | Severity | Component | Affects | Reported on | Published by manufacturer | Published by AOSP |
|---|---|---|---|---|---|---|
| CVE-2023-33066 | HIGH | AUDIO | OS | Mar 21, 2023 | Mar 2024 | Mar 2024 |
| CVE-2020-11170 | CRITICAL | AUDIO | N/A | N/A | Feb 2021 | Feb 2021 |
| CVE-2020-11136 | CRITICAL | AUDIO | OS | N/A | Dec 2020 | Dec 2020 |
| CVE-2020-11137 | CRITICAL | AUDIO | N/A | N/A | Dec 2020 | Dec 2020 |
| CVE-2020-11138 | CRITICAL | AUDIO | N/A | N/A | Dec 2020 | Dec 2020 |
| CVE-2020-11143 | CRITICAL | AUDIO | N/A | N/A | Dec 2020 | Dec 2020 |
| CVE-2020-3685 | CRITICAL | AUDIO | N/A | N/A | Dec 2020 | Dec 2020 |
| CVE-2020-3686 | CRITICAL | AUDIO | N/A | N/A | Dec 2020 | Dec 2020 |
| CVE-2020-3691 | CRITICAL | AUDIO | N/A | N/A | Dec 2020 | Dec 2020 |
| CVE-2013-2596 | N/A | GPU | OS | N/A | N/A | N/A |
11 of 11 row(s) shown.
Rows per page
Page 1 of 2
Devices
| Name | Code name | Manufacturer | Release Date |
|---|---|---|---|
| HTC DROID Incredible 4G LTE | HTC DROID Incredible 4G LTE | HTC | Jul 1, 2012 |
| HTC One X AT&T | HTC One X AT&T | HTC | May 1, 2012 |
| HTC One SV | HTC One SV | HTC | Jan 1, 2013 |
| HTC Evo 4G LTE | HTC Evo 4G LTE | HTC | May 1, 2012 |
| HTC One XL | HTC One XL | HTC | May 1, 2012 |
| Motorola Luge | Motorola Luge | MOTOROLA | Aug 1, 2014 |
| Sony Xperia T LTE | Sony Xperia T LTE | SONY | Nov 1, 2012 |
| Sony Xperia V | LT25i | SONY | Dec 1, 2012 |
| Sony Xperia SX SO-05D | Sony Xperia SX SO-05D | SONY | Sep 1, 2012 |
| Asus Transformer Pad Infinity 700 LTE | Asus Transformer Pad Infinity 700 LTE | ASUS | Dec 1, 2012 |
30 of 30 row(s) shown.
Rows per page
Page 1 of 3
Information reliability
The information on this website is intended to provide information on the big picture of chipset security and measure trends within the industry. Our information is obtained from several vantage points, checked for consistency, and automatically cross-referenced. However, this process may not always yield reliable information. Do not use the information on a particular vulnerability, chipset or device to verify your individual exposure in cases where inaccuracies are inacceptable, for instance to assess risks if you are a Politically Exposed Person.
