LiveActive security incident?Get immediate response
CVE Record

CVE-2023-20610: In display drm, there is a possible memory corruption due to a race condition.

In display drm, there is a possible memory corruption due to a race condition. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07363469; Issue ID: ALPS07363469.

MediumCVSS 6.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw affects MediaTek display driver components on many Android chipsets. A local attacker with already high privileges could trigger memory corruption and potentially gain broader device control. It is not listed as known exploited in the provided sources, but impacted Android fleets should be checked for vendor firmware updates.

Executive priority

Treat as a moderate mobile fleet hygiene issue. It is not evidence of active exploitation, but the potential impact is high on affected devices, especially where untrusted apps or prior compromise are plausible.

Technical view

CVE-2023-20610 is a CWE-662 race condition in MediaTek display DRM that can cause memory corruption. The CVSS 3.1 score is 6.4 with local attack vector, high attack complexity, high privileges required, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to Android 11, 12, or 13 devices using the listed MediaTek chipsets and firmware lacking patch ALPS07363469. Actual exposure depends on OEM firmware packaging and security patch adoption.

Exploitation context

The provided bundle does not show CISA KEV listing or active exploitation. Exploitation is local, requires high privileges, and needs no user interaction, so the highest concern is chained compromise or already-privileged malicious code on affected devices.

Researcher notes

Evidence is vendor-level and sparse. The sources identify the component, race condition class, affected chipsets, Android versions, and patch ID, but do not provide root-cause details, public exploit status, or OEM-specific fixed firmware versions.

Mitigation direction

  • Apply OEM firmware updates that include MediaTek patch ALPS07363469.
  • Check MediaTek and device OEM advisories for fixed builds.
  • Prioritize affected MediaTek Android 11, 12, and 13 devices.
  • Restrict corporate access from devices without current Android security updates.

Validation and detection

  • Inventory Android devices for the listed MediaTek chipsets and Android versions.
  • Verify device firmware includes the February 2023 MediaTek security bulletin fixes.
  • Confirm OEM patch notes reference ALPS07363469 or CVE-2023-20610.
  • Review mobile device management data for outdated Android security patch levels.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-662: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-20610 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.4CVSS 3.1MediumCVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H0.55.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.4Medium
CVSS 3.1 vector shape for CVE-2023-20610Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MediaTek, Inc.MT6761, MT6765, MT6768, MT6779, MT6781, MT6785, MT6789, MT6833, MT6853, MT6855, MT6873, MT6877, MT6879, MT6883, MT6885, MT6889, MT6893, MT6895, MT6983, MT8168, MT8365, MT8675Android 11.0, 12.0, 13.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-662 · source CWE mapping

Improper Synchronization

Improper Synchronization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.