CVE-2025-20705
BaseFortify
Publication date: 2025-09-01
Last updated on: 2025-09-03
Assigner: MediaTek, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linuxfoundation | yocto | 2.6 |
| android | 13.0 | |
| android | 16.0 | |
| openwrt | openwrt | 19.07.0 |
| openwrt | openwrt | 21.02.0 |
| mediatek | mt2718 | * |
| mediatek | mt2735 | * |
| mediatek | mt6739 | * |
| mediatek | mt6761 | * |
| mediatek | mt6765 | * |
| mediatek | mt6768 | * |
| mediatek | mt6781 | * |
| mediatek | mt6789 | * |
| mediatek | mt6835 | * |
| mediatek | mt6853 | * |
| mediatek | mt6855 | * |
| mediatek | mt6877 | * |
| mediatek | mt6878 | * |
| mediatek | mt6879 | * |
| mediatek | mt6880 | * |
| mediatek | mt6883 | * |
| mediatek | mt6885 | * |
| mediatek | mt6886 | * |
| mediatek | mt6889 | * |
| mediatek | mt6890 | * |
| mediatek | mt6893 | * |
| mediatek | mt6895 | * |
| mediatek | mt6897 | * |
| mediatek | mt6899 | * |
| mediatek | mt6980d | * |
| mediatek | mt6983 | * |
| mediatek | mt6985 | * |
| mediatek | mt6989 | * |
| mediatek | mt6990 | * |
| mediatek | mt6991 | * |
| mediatek | mt8169 | * |
| mediatek | mt8186 | * |
| mediatek | mt8188 | * |
| mediatek | mt8676 | * |
| mediatek | mt8678 | * |
| mediatek | mt8696 | * |
| mediatek | mt8775 | * |
| mediatek | mt8792 | * |
| mediatek | mt8796 | * |
| android | 14.0 | |
| android | 15.0 |
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 use-after-free memory corruption issue in the monitor_hang component. It occurs when memory is accessed after it has been freed, which can cause unexpected behavior or crashes.
How can this vulnerability impact me? :
If exploited, this vulnerability could lead to local escalation of privilege, but only if a malicious actor already has System privilege. No user interaction is needed for exploitation.
What immediate steps should I take to mitigate this vulnerability?
Apply the patch identified as ALPS09989078 provided by the vendor to fix the memory corruption issue in monitor_hang. Since exploitation does not require user interaction but requires prior System privilege, ensure that systems are updated promptly and restrict access to System privileges to trusted users only.