| CVE-2026-20445 |
In MDDP, there is a possible system crash due to a race condition
|
4.4
Moyenne
|
2 mars 2026 |
| CVE-2026-20429 |
In display, there is a possible out of bounds read due to a missing bounds check
|
4.4
Moyenne
|
2 mars 2026 |
| CVE-2026-20444 |
In display, there is a possible memory corruption due to a missing bounds check
|
6.7
Moyenne
|
2 mars 2026 |
| CVE-2026-20443 |
In display, there is a possible memory corruption due to use after free
|
6.7
Moyenne
|
2 mars 2026 |
| CVE-2026-20442 |
In display, there is a possible system crash due to use after free
|
4.4
Moyenne
|
2 mars 2026 |
| CVE-2026-20434 |
In Modem, there is a possible out of bounds write due to a missing bounds check
|
7.5
Élevée
|
2 mars 2026 |
| CVE-2026-20428 |
In display, there is a possible out of bounds write due to a missing bounds check
|
6.7
Moyenne
|
2 mars 2026 |
| CVE-2026-20427 |
In display, there is a possible escalation of privilege due to a missing bounds check
|
6.7
Moyenne
|
2 mars 2026 |
| CVE-2026-20426 |
In display, there is a possible out of bounds write due to a missing bounds check
|
6.7
Moyenne
|
2 mars 2026 |
| CVE-2026-20425 |
In display, there is a possible out of bounds write due to a missing bounds check
|
6.7
Moyenne
|
2 mars 2026 |
| CVE-2026-20406 |
In Modem, there is a possible system crash due to an uncaught exception
|
6.5
Moyenne
|
2 févr. 2026 |
| CVE-2026-20405 |
In Modem, there is a possible system crash due to a missing bounds check
|
6.5
Moyenne
|
2 févr. 2026 |
| CVE-2026-20404 |
In Modem, there is a possible system crash due to improper input validation
|
6.5
Moyenne
|
2 févr. 2026 |
| CVE-2026-20403 |
In Modem, there is a possible system crash due to a missing bounds check
|
6.5
Moyenne
|
2 févr. 2026 |
| CVE-2026-20422 |
In Modem, there is a possible system crash due to improper input validation
|
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-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 |