| CVE-2024-20053 |
In flashc, there is a possible out of bounds write due to an uncaught exception
|
8.4
Élevée
|
1 avr. 2024 |
| CVE-2024-20048 |
In flashc, there is a possible information disclosure due to an uncaught exception
|
6.2
Moyenne
|
1 avr. 2024 |
| CVE-2024-20041 |
In da, there is a possible out of bounds read due to a missing bounds check
|
4.4
Moyenne
|
1 avr. 2024 |
| CVE-2024-20040 |
In wlan firmware, there is a possible out of bounds write due to improper input validation
|
8.8
Élevée
|
1 avr. 2024 |
| CVE-2024-20037 |
In pq, there is a possible write-what-where condition due to an incorrect bounds check
|
6.7
Moyenne
|
4 mars 2024 |
| CVE-2024-20036 |
In vdec, there is a possible permission bypass due to a permissions bypass
|
4.4
Moyenne
|
4 mars 2024 |
| CVE-2024-20032 |
In aee, there is a possible permission bypass due to a missing permission check
|
6.7
Moyenne
|
4 mars 2024 |
| CVE-2024-20023 |
In flashc, there is a possible out of bounds write due to lack of valudation
|
6.7
Moyenne
|
4 mars 2024 |
| CVE-2024-20022 |
In lk, there is a possible escalation of privilege due to a missing bounds check
|
6.7
Moyenne
|
4 mars 2024 |
| CVE-2024-20016 |
In ged, there is a possible out of bounds write due to an integer overflow
|
4.4
Moyenne
|
5 févr. 2024 |
| CVE-2024-20015 |
In telephony, there is a possible escalation of privilege due to a permissions bypass
|
7.4
Élevée
|
5 févr. 2024 |
| CVE-2023-32865 |
In display drm, there is a possible out of bounds write due to an incorrect bounds check
|
Non notée
|
4 déc. 2023 |
| CVE-2023-32845 |
In 5G Modem, there is a possible system crash due to improper error handling
|
Non notée
|
4 déc. 2023 |
| CVE-2023-32856 |
In display, there is a possible out of bounds read due to an incorrect status check
|
Non notée
|
4 déc. 2023 |
| CVE-2023-32840 |
In modem CCCI, there is a possible out of bounds write due to a missing bounds check
|
8.4
Élevée
|
6 nov. 2023 |
| CVE-2023-20702 |
In 5G NRLC, there is a possible invalid memory access due to lack of error handling
|
7.5
Élevée
|
6 nov. 2023 |
| CVE-2023-32829 |
In apusys, there is a possible out of bounds write due to an integer overflow
|
6.7
Moyenne
|
2 oct. 2023 |
| CVE-2023-32827 |
In camera middleware, there is a possible out of bounds write due to a missing input validation
|
6.7
Moyenne
|
2 oct. 2023 |
| CVE-2023-32826 |
In camera middleware, there is a possible out of bounds write due to a missing input validation
|
6.7
Moyenne
|
2 oct. 2023 |
| CVE-2023-32824 |
In rpmb , there is a possible double free due to improper locking
|
6.7
Moyenne
|
2 oct. 2023 |
| CVE-2023-32823 |
In rpmb , there is a possible memory corruption due to a missing bounds check
|
6.7
Moyenne
|
2 oct. 2023 |
| CVE-2023-32822 |
In ftm, there is a possible out of bounds write due to a missing bounds check
|
6.7
Moyenne
|
2 oct. 2023 |
| CVE-2023-32820 |
In wlan firmware, there is a possible firmware assertion due to improper input handling
|
7.5
Élevée
|
2 oct. 2023 |
| CVE-2023-20819 |
In CDMA PPP protocol, there is a possible out of bounds write due to a missing bounds check
|
6.7
Moyenne
|
2 oct. 2023 |
| CVE-2023-20832 |
In gps, there is a possible out of bounds write due to a missing bounds check
|
6.7
Moyenne
|
4 sept. 2023 |