| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in MediaTek MT6739, MT6761, MT6765, MT6768, MT6781, MT6789, MT6833, MT6835, MT6853, MT6855, MT6877, MT6878, MT6879, MT6883, MT6885, MT6886, MT6889, MT6893, MT6895, MT6897, MT6899, MT6983, MT6985, MT6989 and MT6991. It has been classified as critical. The impacted element is an unknown function of the component Display. The manipulation leads to out-of-bounds. This vulnerability is traded as CVE-2025-20768. An attack has to be approached locally. There is no exploit available. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in MediaTek MT6739, MT6761, MT6765, MT6768, MT6781, MT6789, MT6833, MT6835, MT6853, MT6855, MT6877, MT6878, MT6879, MT6883, MT6885, MT6886, MT6889, MT6893, MT6895, MT6897, MT6899, MT6983, MT6985, MT6989 and MT6991. It has been rated as critical. This issue affects an unknown code block of the component Display. The manipulation with an unknown input leads to a out-of-bounds vulnerability. Using CWE to declare the problem leads to CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
In display, there is a possible out of bounds read due to a missing bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained the System privilege. User interaction is not needed for exploitation. Patch ID: ALPS10196993; Issue ID: MSV-4805.
The advisory is shared at corp.mediatek.com. The identification of this vulnerability is CVE-2025-20768 since 11/01/2024. The exploitation is known to be easy. An attack has to be approached locally. Additional levels of successful authentication are needed for exploitation. Neither technical details nor an exploit are publicly available.
Applying the patch ALPS10196993 is able to eliminate this problem.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-200157). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
- MT6739
- MT6761
- MT6765
- MT6768
- MT6781
- MT6789
- MT6833
- MT6835
- MT6853
- MT6855
- MT6877
- MT6878
- MT6879
- MT6883
- MT6885
- MT6886
- MT6889
- MT6893
- MT6895
- MT6897
- MT6899
- MT6983
- MT6985
- MT6989
- MT6991
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.7VulDB Meta Temp Score: 6.4
VulDB Base Score: 6.7
VulDB Temp Score: 6.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Out-of-boundsCWE: CWE-125 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔒
Patch: ALPS10196993
Timeline
11/01/2024 CVE reserved12/02/2025 Advisory disclosed
12/02/2025 VulDB entry created
12/03/2025 VulDB entry last update
Sources
Advisory: MSV-4805Status: Confirmed
CVE: CVE-2025-20768 (🔒)
GCVE (CVE): GCVE-0-2025-20768
GCVE (VulDB): GCVE-100-333989
EUVD: 🔒
Entry
Created: 12/02/2025 07:57Updated: 12/03/2025 08:26
Changes: 12/02/2025 07:57 (56), 12/03/2025 08:26 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.