LiveActive security incident?Get immediate response
CVE Record

CVE-2021-0872: In PVRSRVBridgeRGXKickVRDM of the PowerVR kernel driver, a missing size check means there is a possible int...

In PVRSRVBridgeRGXKickVRDM of the PowerVR kernel driver, a missing size check means there is a possible integer overflow that could allow out-of-bounds heap access. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android SoCAndroid ID: A-270401229

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-0872 is a local privilege escalation flaw in Android SoC devices using the PowerVR kernel driver. A malicious local app or process could potentially gain higher privileges through a driver integer overflow. The source bundle does not identify specific device models or active exploitation.

Executive priority

Prioritize this for Android fleets where unmanaged apps or sensitive data are present. Business urgency is high for affected devices, but scope is uncertain because the public sources do not identify exact models.

Technical view

The flaw is in PVRSRVBridgeRGXKickVRDM in the PowerVR kernel driver. A missing size check can trigger integer overflow and out-of-bounds heap access. CVSS 3.1 is 7.8 with local attack vector, low privileges, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to Android SoC implementations that include the affected PowerVR kernel driver. The provided sources do not list specific OEMs, chipsets, kernels, or device models, so teams must validate against their Android fleet and vendor security bulletins.

Exploitation context

The source bundle supports local escalation of privilege with low privileges and no user interaction. It does not show remote exploitation, public exploit availability, or CISA KEV listing. Treat exploitation status as unconfirmed, not actively exploited.

Researcher notes

Key uncertainty is asset mapping: the CVE names Android SoC and PowerVR kernel driver, not specific devices. Validation should focus on kernel driver presence, OEM patch lineage, and April 2023 Android bulletin coverage without assuming broader Android impact.

Mitigation direction

  • Apply OEM Android security updates covering the April 2023 Android Security Bulletin.
  • Check device vendor advisories for affected models and exact patch availability.
  • Prioritize managed Android devices with PowerVR-based SoCs or unknown SoC inventory.
  • Restrict untrusted app installation until devices are confirmed patched.

Validation and detection

  • Inventory Android devices, SoC families, OEMs, and Android security patch levels.
  • Confirm whether devices include the PowerVR kernel driver path referenced by the advisory.
  • Verify patch status against the April 2023 Android Security Bulletin and OEM release notes.
  • Track unpatchable or unsupported devices for replacement or isolation decisions.
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.

cwe · low confidence lookup

CWE-190: 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-2021-0872 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/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
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2021-0872Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/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
n/aAndroidAndroid SoCListed
Weakness

CWE details

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