| CVE-2026-20401 |
In Modem, there is a possible system crash due to an uncaught exception
|
6.5
Moyenne
|
2 févr. 2026 |
| CVE-2026-20420 |
In Modem, there is a possible system crash due to incorrect error handling
|
6.5
Moyenne
|
2 févr. 2026 |
| CVE-2025-20807 |
In dpe, there is a possible out of bounds write due to an integer overflow
|
6.7
Moyenne
|
6 janv. 2026 |
| CVE-2025-20806 |
In dpe, there is a possible memory corruption due to use after free
|
6.7
Moyenne
|
6 janv. 2026 |
| CVE-2025-20805 |
In dpe, there is a possible memory corruption due to use after free
|
6.7
Moyenne
|
6 janv. 2026 |
| CVE-2025-20804 |
In dpe, there is a possible memory corruption due to use after free
|
6.7
Moyenne
|
6 janv. 2026 |
| CVE-2025-20803 |
In dpe, there is a possible memory corruption due to an integer overflow
|
6.7
Moyenne
|
6 janv. 2026 |
| CVE-2025-20787 |
In display, there is a possible memory corruption due to use after free
|
6.7
Moyenne
|
6 janv. 2026 |
| CVE-2025-20786 |
In display, there is a possible memory corruption due to use after free
|
6.7
Moyenne
|
6 janv. 2026 |
| CVE-2025-20785 |
In display, there is a possible memory corruption due to use after free
|
6.7
Moyenne
|
6 janv. 2026 |
| CVE-2025-20784 |
In display, there is a possible memory corruption due to uninitialized data
|
6.7
Moyenne
|
6 janv. 2026 |
| CVE-2025-20783 |
In display, there is a possible out of bounds write due to a missing bounds check
|
6.7
Moyenne
|
6 janv. 2026 |
| 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-20802 |
In geniezone, there is a possible memory corruption due to use after free
|
6.7
Moyenne
|
6 janv. 2026 |
| CVE-2025-20801 |
In seninf, there is a possible memory corruption due to a race condition
|
7.0
Élevée
|
6 janv. 2026 |
| CVE-2025-20800 |
In mminfra, there is a possible out of bounds write due to a missing bounds check
|
7.8
Élevée
|
6 janv. 2026 |
| CVE-2025-20799 |
In c2ps, there is a possible memory corruption due to use after free
|
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-20796 |
In imgsys, there is a possible out of bounds write due to improper input validation
|
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 |