CVE-2023-32824

Local privilege escalation via improperly locked double free

Published Oct 2, 2023 · Updated Sep 28, 2024

Double free in the rpmb component on affected MediaTek chipsets running Android 12.0 or 13.0 allows local users to escalate privileges. Improper locking in rpmb permits the same allocation to be released twice during concurrent access, corrupting memory. Exploitation requires existing System execution privileges and no user interaction, and the resulting escalation is local to the device.

CVSS severity6.7
Medium
EPSS probability0.08%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Double free in the rpmb component on affected MediaTek chipsets running Android 12.0 or 13.0 allows local users to escalate privileges. Improper locking in rpmb permits the same allocation to be released twice during concurrent access, corrupting memory. Exploitation requires existing System execution privileges and no user interaction, and the resulting escalation is local to the device.

The record

CVE
CVE-2023-32824
Published
Oct 2, 2023
Updated
Sep 28, 2024
Vendor
MediaTek
Product
MT6889
Classifications
CWE-415, T1068
Attack vector
local
Privileges
admin

Timeline

How it unfolded

  1. Oct 2, 2023CVE publishedPublication date reported by the CVE source.
  2. Sep 28, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <=*

What conditions does exploitation require?

Attack vectorlocal
Required privilegesadmin

What is affected?

MediaTek · MT6889version=0 <=*
MediaTek · MT6875version=0 <=*
MediaTek · MT6789version=0 <=*
MediaTek · MT6891version=0 <=*
MediaTek · MT6768version=0 <=*
MediaTek · MediaTek MT6785version=0 <=*
MediaTek · MT6853Tversion=0 <=*
MediaTek · MT6855version=0 <=*
MediaTek · MediaTek MT6765version=0 <=*
MediaTek · MT6893version=0 <=*
MediaTek · MT6885version=0 <=*
MediaTek · MT6769version=0 <=*
MediaTek · MT8666version=0 <=*
MediaTek · MT6879version=0 <=*
MediaTek · MT6873version=0 <=*
MediaTek · MT6781version=0 <=*
MediaTek · MT6739version=0 <=*
MediaTek · MT6877version=0 <=*
MediaTek · MediaTek MT6761version=0 <=*
Google · Androidversion=12.0; version=13.0
MediaTek · MediaTek MT6762version=0 <=*
MediaTek · MT6853version=0 <=*
MediaTek · MT6883version=0 <=*
MediaTek · MT6985version=0 <=*
MediaTek · MT8788version=0 <=*
MediaTek · MT6833version=0 <=*
MediaTek · MT6983version=0 <=*
MediaTek · MediaTek MT6580version=0 <=*
MediaTek · MT8765version=0 <=*
MediaTek · MediaTek MT6779version=0 <=*
MediaTek · MT6895version=0 <=*

Published CVSS scores

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

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesadmin
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-415Double Free
T1068Exploitation for Privilege Escalation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo