LiveActive security incident?Get immediate response
CVE Record

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

In PVRSRVBridgeRGXKickSync 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-270395803

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-0882 is an Android SoC kernel driver flaw involving PowerVR graphics code. A malicious local app could potentially gain higher privileges on an affected device without user interaction. The business risk is strongest for Android fleets with vulnerable SoC vendor firmware that has not absorbed the Android April 2023 security fixes.

Executive priority

Treat this as a high-priority mobile fleet patching issue, especially for Android devices with unknown SoC firmware status. It is not a remote internet-facing bug, but local privilege escalation can materially increase impact after app compromise.

Technical view

The issue is in PVRSRVBridgeRGXKickSync in the PowerVR kernel driver. A missing size check can cause integer overflow and out-of-bounds heap access, leading to local privilege escalation. CVSS 3.1 is 7.8: local attack vector, low complexity, low privileges required, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to Android SoC builds using the affected PowerVR kernel driver. The sources do not identify specific device models, chipsets, or OEM firmware versions, so validation must be device- and vendor-specific.

Exploitation context

The provided sources do not report active exploitation, and the CVE is not marked as CISA KEV. Exploitation is local and requires some existing low-privileged execution on the device, such as a malicious or compromised app.

Researcher notes

Core evidence is strong for the vulnerability class, affected Android SoC context, and severity. Public scope is incomplete: the bundle does not name exact OEMs, devices, chips, fixed commits, or exploit availability. Avoid assuming universal Android exposure.

Mitigation direction

  • Apply OEM firmware updates covering the April 2023 Android Security Bulletin.
  • Confirm vendor SoC security patches include CVE-2021-0882.
  • Prioritize managed Android devices using PowerVR graphics drivers.
  • Restrict untrusted app installation where patching is delayed.
  • Replace or isolate unsupported devices that cannot receive vendor fixes.

Validation and detection

  • Inventory Android devices, SoC families, GPU drivers, and patch levels.
  • Check OEM advisories for CVE-2021-0882 coverage on each device model.
  • Verify Android security patch level against vendor fixed releases.
  • Review MDM data for devices blocked from current firmware updates.
  • Document exceptions where device applicability cannot be confirmed.
Prepared
Confidence
high
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-0882 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-0882Attack 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.

CWE-190 · source CWE mapping

Integer Overflow or Wraparound

Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.