MT
Product
Mt6880
21
CVEs
0
On KEV
9.8
Max CVSS
0
New 30D
Severity mix
Critical 2High 5Medium 14Low 0
Watch
Add Mt6880 to your stack to get only the CVEs that touch what you run.
| CVE | CVSS | Published | Summary · affected versions |
|---|---|---|---|
| CVE-2024-20081 | 6.7 | Jul 1 | In gnss service, there is a possible out of bounds write due to improper input validation Affected: All versions, or not specified |
| CVE-2024-20056 | 6.7 | May 6 | In preloader, there is a possible escalation of privilege due to an insecure default value Affected: android_12.0 through android_14.0 |
| CVE-2024-20023 | 6.7 | Mar 4 | In flashc, there is a possible out of bounds write due to lack of valudation Affected: 0 |
| CVE-2024-20022 | 6.7 | Mar 4 | In lk, there is a possible escalation of privilege due to a missing bounds check Affected: 0 |
| CVE-2024-20006 | 6.7 | Feb 5 | In da, there is a possible out of bounds write due to a missing bounds check Affected: All versions, or not specified |
| CVE-2023-20832 | 6.7 | Sep 4 | In gps, there is a possible out of bounds write due to a missing bounds check Affected: 0 |
| CVE-2023-20831 | 6.7 | Sep 4 | In gps, there is a possible out of bounds write due to a missing bounds check Affected: 0 |
| CVE-2023-20830 | 6.7 | Sep 4 | In gps, there is a possible out of bounds write due to a missing bounds check Affected: 0 |
| CVE-2023-20829 | 6.7 | Sep 4 | In gps, there is a possible out of bounds write due to a missing bounds check Affected: 0 |
| CVE-2023-20828 | 6.7 | Sep 4 | In gps, there is a possible out of bounds write due to a missing bounds check Affected: 0 |
| CVE-2023-20821 | 6.7 | Sep 4 | In nvram, there is a possible out of bounds write due to a missing bounds check Affected: 0 |
| CVE-2023-32840 | 6.5 | Nov 6 | In modem CCCI, there is a possible out of bounds write due to a missing bounds check Affected: 0 |
| CVE-2024-20136 | 6.2 | Dec 2 | In da, there is a possible out of bounds read due to a missing bounds check Affected: 0 |
| CVE-2023-32871 | 5.3 | May 6 | In DA, there is a possible permission bypass due to an incorrect status check Affected: android_11.0 through android_14.0 |
Showing 14