CVE-2026-20415 Details
Description
In imgsys, there is a possible memory corruption due to improper locking. This could lead to local denial of service if a malicious actor has already obtained the System privilege. User interaction is not needed for exploitation. Patch ID: ALPS10363254; Issue ID: MSV-5617.
A memory corruption vulnerability has been identified in the imgsys component of certain MediaTek chipsets, including MT6897 and MT6989. This vulnerability arises from improper locking, which could allow a malicious actor with System privileges to cause a local denial-of-service. The issue does not require user interaction for exploitation.
Device OEMs have been notified of this vulnerability and the corresponding security patches are available. For further information, OEMs can contact their MediaTek representative.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Feb 2, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://corp.mediatek.com/product-security-bulletin/February-2026 | [email protected] | Vendor Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-667 | Improper Locking | [email protected] |
| CWE-415 | Double Free | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| google android | 15.0 |
CPE
Remediation
| |
| mediatek mt6897 | All versions |
CPE
Remediation
| |
| mediatek mt6989 | All versions |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Feb 3, 2026 | Initial Analysis | [email protected] |
| Feb 2, 2026 | CVE Modified | CISA-ADP |
| Feb 2, 2026 | New CVE Received | [email protected] |