CVE-2025-20780
BaseFortify
Publication date: 2026-01-06
Last updated on: 2026-01-08
Assigner: MediaTek, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| android | 15.0 | |
| android | 16.0 | |
| mediatek | mt6739 | * |
| mediatek | mt6761 | * |
| mediatek | mt6765 | * |
| mediatek | mt6768 | * |
| mediatek | mt6781 | * |
| mediatek | mt6789 | * |
| mediatek | mt6833 | * |
| mediatek | mt6835 | * |
| mediatek | mt6853 | * |
| mediatek | mt6855 | * |
| mediatek | mt6877 | * |
| mediatek | mt6878 | * |
| mediatek | mt6879 | * |
| mediatek | mt6883 | * |
| mediatek | mt6885 | * |
| mediatek | mt6886 | * |
| mediatek | mt6889 | * |
| mediatek | mt6893 | * |
| mediatek | mt6895 | * |
| mediatek | mt6897 | * |
| mediatek | mt6899 | * |
| mediatek | mt6983 | * |
| mediatek | mt6985 | * |
| mediatek | mt6989 | * |
| mediatek | mt6991 | * |
| mediatek | mt8186 | * |
| mediatek | mt8188 | * |
| mediatek | mt8196 | * |
| mediatek | mt8667 | * |
| mediatek | mt8673 | * |
| mediatek | mt8676 | * |
| mediatek | mt8678 | * |
| mediatek | mt8765 | * |
| mediatek | mt8766 | * |
| mediatek | mt8768 | * |
| mediatek | mt8771 | * |
| mediatek | mt8781 | * |
| mediatek | mt8791t | * |
| mediatek | mt8792 | * |
| mediatek | mt8793 | * |
| mediatek | mt8795t | * |
| mediatek | mt8796 | * |
| mediatek | mt8798 | * |
| mediatek | mt8873 | * |
| mediatek | mt8883 | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a memory corruption issue caused by a use after free error in the display component. It occurs when the system accesses memory that has already been freed, potentially leading to unexpected behavior or crashes.
How can this vulnerability impact me? :
If exploited, this vulnerability could allow a local attacker who already has System privileges to escalate their privileges further. No user interaction is required for exploitation.
What immediate steps should I take to mitigate this vulnerability?
Apply the patch identified as ALPS10184061 to fix the memory corruption issue. Since the vulnerability allows local escalation of privilege without user interaction, ensure that all systems are updated promptly to prevent exploitation.