LiveActive security incident?Get immediate response
CVE Record

CVE-2021-0540: In halWrapperDataCallback of hal_wrapper.cc, there is a possible out of bounds write due to a missing bound...

In halWrapperDataCallback of hal_wrapper.cc, there is a possible out of bounds write 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.Product: AndroidVersions: Android-11Android ID: A-169328517

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-0540 is an Android 11 flaw in a hardware abstraction wrapper component. The public description says a missing bounds check could allow an out-of-bounds write and local privilege escalation. Exploitation is not described as remote and requires System execution privileges, so business urgency depends on whether affected Android 11 devices remain unpatched.

Executive priority

Handle as a mobile endpoint patching and lifecycle issue. Escalate priority if business-critical Android 11 devices remain unpatched, unmanaged, or unsupported, but current public evidence does not support emergency exploitation response.

Technical view

The issue is in halWrapperDataCallback in hal_wrapper.cc. A missing bounds check can cause an out-of-bounds write. The stated impact is local escalation of privilege, with System execution privileges needed and no user interaction required. The source bundle provides no CVSS, CWE, exploit details, or device-specific affected matrix beyond Android 11.

Likely exposure

Exposure is most relevant to Android 11 devices, especially Pixel or Android builds governed by the June 2021 Android/Pixel security bulletin. The sources do not identify other Android versions, downstream OEM status, or specific chipsets.

Exploitation context

The sources do not report active exploitation, and the CVE is not listed as KEV in the provided bundle. The described attack context is local privilege escalation, not network exploitation. Existing System-level execution privileges are stated as required.

Researcher notes

Evidence is limited. The public description names the vulnerable callback and bug class but does not provide patch diff, CVSS scoring, CWE mapping, affected OEM variants, or exploitability details beyond local EoP with System privileges needed.

Mitigation direction

  • Identify Android 11 devices in fleet and ownership scope.
  • Apply relevant Android or Pixel security updates from June 2021 or later.
  • Check OEM advisories for device-specific patch availability and build numbers.
  • Prioritize unsupported Android 11 devices for upgrade, replacement, or isolation.

Validation and detection

  • Confirm device OS version, security patch level, and OEM build identifier.
  • Verify affected devices show a security patch level including June 2021 or later guidance.
  • Review mobile device management inventory for remaining Android 11 endpoints.
  • Document exceptions where OEM patch status cannot be confirmed.
Prepared
Confidence
medium
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.

cve · low confidence lookup

CVE-2021-0540 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

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

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aAndroidAndroid-11Listed
Weakness

CWE details

No CWE listed

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