LiveActive security incident?Get immediate response
CVE Record

CVE-2021-0873: In PVRSRVBridgeRGXKickRS of the PowerVR kernel driver, a missing size check means there is a possible integ...

In PVRSRVBridgeRGXKickRS 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-270392711

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is an Android SoC vulnerability in a PowerVR kernel graphics driver. A local app or attacker with basic local access could trigger an integer overflow leading to out-of-bounds heap access and possible device privilege escalation. No user interaction is required.

Executive priority

Treat as high priority for Android fleets because it can enable local privilege escalation on affected devices. Business urgency depends on whether your deployed devices use the affected SoC or driver and whether April 2023 or later security updates are installed.

Technical view

CVE-2021-0873 affects PVRSRVBridgeRGXKickRS in the PowerVR kernel driver. Missing size validation can cause CWE-190 integer overflow and out-of-bounds heap access. The CVSS 3.1 vector is local, low complexity, low privileges, no user interaction, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely on Android devices using affected SoC components with the vulnerable PowerVR kernel driver. The source bundle does not identify specific OEM models, chipsets, or Android releases beyond Android SoC.

Exploitation context

The CVE describes local escalation of privilege with no additional execution privileges and no user interaction. CISA KEV is false in the provided bundle, and no cited source confirms active exploitation.

Researcher notes

The public record gives the vulnerable bridge function, weakness class, Android ID A-270392711, and impact, but not model-level affected device data or exploit details. Validation should stay focused on patch provenance and vendor applicability rather than exploit reproduction.

Mitigation direction

  • Apply Android or OEM security updates covering the April 2023 Android Security Bulletin.
  • Check device vendor guidance when patch availability is unclear.
  • Prioritize managed Android fleets using affected SoC or PowerVR components.
  • Restrict untrusted app installation on devices awaiting updates.

Validation and detection

  • Inventory Android devices by OEM, model, SoC, GPU, and security patch level.
  • Confirm installed updates include the April 2023 Android Security Bulletin fix.
  • Review OEM advisories for device-specific applicability and patch naming.
  • Use MDM reporting to identify devices below the required patch level.
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-0873 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-0873Attack 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.