dbcve.org
AndroidOperating system · Google

CVE-2023-32863

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 read due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07326314; Issue ID: ALPS07326314.

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 missing bounds check in the Linux kernel's Direct Rendering Manager (DRM) display subsystem allows an out-of-bounds read vulnerability. This could enable a local attacker with System execution privileges to potentially escalate privileges or cause a denial of service by reading memory beyond allocated buffers.

MitigationApply the provided kernel patch (ALPS07326314) to address the missing bounds check in the DRM display code and update to the patched kernel version.

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
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via adb shell
    Affected if The version is exactly 12.0 or 13.0 (exact match per affected versions)
  2. Verify kernel patch status
    Check if kernel security patches include ALPS07326314 - run 'getprop ro.build.version.security_patch' or check kernel build config for the bounds check fix in DRM display code
    Affected if Kernel is unpatched and does not contain the ALPS07326314 fix for the missing bounds check
  3. Confirm DRM display subsystem presence
    Check if the device uses the vulnerable DRM display code - look for 'drm' in /proc/modules or check kernel config for CONFIG_DRM and display-related modules
    Affected if DRM subsystem is loaded and the vulnerable bounds-check code path is present
  4. Verify execution context
    The vulnerability requires System-level privileges to exploit - confirm the attacker's privilege level via 'whoami' or process UID checks
    Affected if Attacker has System execution privileges (UID 1000) or root access

User is affected if Android version is exactly 12.0 or 13.0 AND the kernel lacks the ALPS07326314 patch for the DRM display bounds check vulnerability.

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 provided kernel patch (ALPS07326314) to address the missing bounds check in the DRM display code and update to the patched kernel version.

Recommended fix High confidence

Android 14 (when available from device manufacturer with December 2023 or later security patch level)

  1. Check if your device receives monthly Android Security Patch Levels (SPL) from your device manufacturer
  2. Contact your device manufacturer (OEM) to confirm if the MediaTek display DRM patch (ALPS07326314) is included in their latest security update
  3. If your device manufacturer has released a security update containing this patch, apply the update immediately
  4. For enterprise or custom deployments, verify the MediaTek security bulletin for the specific build numbers containing the fix
  5. If no manufacturer update is available, consider using a device that receives regular security updates or contact the device vendor for timeline
Caveat None expected - this is a security patch within same Android major version; verify app compatibility if using custom ROMs

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-32863 — 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-32863 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