CVE-2024-20105: MediaTek MT6580, MT6739, MT6761, MT6765, MT6768, MT6779, MT6781, MT6785, MT6789, MT6833, MT6853, MT6855, MT6873, MT6877, MT6879, MT6883, MT6885, MT6889, MT6893, MT6895, MT6983, MT8666, MT8667, MT8673, MT8768 · Out-of-bounds Write
Affects MediaTek MT6580, MT6739, MT6761, MT6765, MT6768, MT6779, MT6781, MT6785, MT6789, MT6833, MT6853, MT6855, MT6873, MT6877, MT6879, MT6883, MT6885, MT6889, MT6893, MT6895, MT6983, MT8666, MT8667, MT8673, MT8768Source CVE Database V5
Not known to be exploited · CVSS 6.7 Medium.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.08% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 6 Jan 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| MediaTek, Inc. MT6580, MT6739, MT6761, MT6765, MT6768, MT6779, MT6781, MT6785, MT6789, MT6833, MT6853, MT6855, MT6873, MT6877, MT6879, MT6883, MT6885, MT6889, MT6893, MT6895, MT6983, MT8666, MT8667, MT8673, MT8768 | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2024-20105, organizations and device manufacturers should promptly apply the official patches provided by MediaTek (patch ID ALPS09062027) as soon as they become available for their devices. Device vendors should ensure timely firmware and OS updates are distributed to end users. Restricting System-level privileges is critical; administrators should enforce the principle of least privilege and harden access controls to prevent unauthorized elevation to System privileges. Employ runtime protections such as memory protection mechanisms (e.g., DEP, ASLR) and integrity monitoring to detect anomalous behavior indicative of exploitation attempts. Regularly audit devices for signs of compromise and privilege escalation. For enterprises managing fleets of devices, implement Mobile Device Management (MDM) solutions to enforce patch compliance and monitor security posture. Additionally, educating users and administrators about the risks of privilege escalation and securing local access can reduce the likelihood of initial System-level compromise. Finally, coordinate with chipset vendors and OS providers to stay informed about updates and advisories related to this vulnerability.
Description
In m4u, there is a possible out of bounds write 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: ALPS09062027; Issue ID: MSV-1743.