dbcve.org
AndroidOperating system · Google

CVE-2023-32865

MEDIUM · 6.7 CVSS v3.1 Published 2023-12-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In display drm, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07363456; Issue ID: ALPS07363456.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A vulnerability in the display Direct Rendering Manager (DRM) allows an out-of-bounds write due to an incorrect bounds check. This kernel-level flaw enables a local attacker to escalate privileges to System level without requiring user interaction. The vulnerability stems from insufficient boundary validation in the graphics display driver code.

MitigationApply the vendor-specific patch ALPS07363456, which corrects the bounds check logic in the display DRM component. Since this is a kernel-level privilege escalation vulnerability, prioritize rapid patch deployment to affected systems.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AndroidOperating system
Affected:= 12.0= 13.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Android version
    Navigate to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if Version is exactly 12.0 or 13.0
  2. Verify kernel version
    Run 'uname -r' or 'cat /proc/version' via ADB shell to identify the kernel build
    Affected if Kernel version corresponds to the vulnerable Android releases (12.0/13.0) and contains the unpatched DRM display driver
  3. Confirm DRM display driver presence
    Check for the presence of the graphics DRM driver module by running 'ls /sys/class/drm' or 'cat /proc/modules' via ADB shell
    Affected if DRM graphics driver is loaded and the system is running an affected Android version

The environment is affected if the device runs Android 12.0 or 13.0 with the vulnerable kernel-level DRM display driver present and no vendor patch applied.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-specific patch ALPS07363456, which corrects the bounds check logic in the display DRM component. Since this is a kernel-level privilege escalation vulnerability, prioritize rapid patch deployment to affected systems.

Recommended fix Moderate confidence

Latest Android security update from OEM containing MediaTek patch ALPS07363456 (typically June 2023 or later security patch level)

  1. 1. Check if your Android device uses a MediaTek chipset (processor) by going to Settings > About Phone > Processor or Chipset.
  2. 2. Verify the current Android security patch level by going to Settings > About Phone > Security Patch Level.
  3. 3. Contact your device manufacturer (OEM) to confirm they have released a security update containing the MediaTek patch ALPS07363456.
  4. 4. Apply the latest available Android security update from your device manufacturer. This update should include the fix for CVE-2023-32865.
  5. 5. After updating, confirm the security patch level includes the month when the fix was released (typically the patch was included in Android security bulletins following the disclosure).
Caveat Security updates from OEM are generally low-risk; updating to latest security patch is recommended. Some older devices may stop receiving updates.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-32865 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-32865 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data