| CVE-2025-20782 |
In display, there is a possible out of bounds write due to a missing bounds check
|
6.7
Moyenne
|
6 janv. 2026 |
| CVE-2025-20781 |
In display, there is a possible memory corruption due to use after free
|
7.8
Élevée
|
6 janv. 2026 |
| CVE-2025-20780 |
In display, there is a possible memory corruption due to use after free
|
7.8
Élevée
|
6 janv. 2026 |
| CVE-2025-20779 |
In display, there is a possible use after free due to a race condition
|
7.0
Élevée
|
6 janv. 2026 |
| CVE-2025-20778 |
In display, there is a possible out of bounds write due to a missing bounds check
|
7.8
Élevée
|
6 janv. 2026 |
| CVE-2025-20798 |
In battery, there is a possible out of bounds write due to a missing bounds check
|
7.8
Élevée
|
6 janv. 2026 |
| CVE-2025-20797 |
In battery, there is a possible out of bounds write due to a missing bounds check
|
7.8
Élevée
|
6 janv. 2026 |
| CVE-2025-20760 |
In Modem, there is a possible read of uninitialized heap data due to an uncaught exception
|
6.5
Moyenne
|
6 janv. 2026 |
| CVE-2025-20761 |
In Modem, there is a possible system crash due to incorrect error handling
|
6.5
Moyenne
|
6 janv. 2026 |
| CVE-2025-20793 |
In Modem, there is a possible system crash due to incorrect error handling
|
6.5
Moyenne
|
6 janv. 2026 |
| CVE-2025-20794 |
In Modem, there is a possible system crash due to improper input validation
|
6.5
Moyenne
|
6 janv. 2026 |
| CVE-2025-20795 |
In KeyInstall, there is a possible out of bounds write due to a missing bounds check
|
7.8
Élevée
|
6 janv. 2026 |