LiveActive security incident?Get immediate response
CVE Record

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

In PVRSRVBridgeChangeSparseMem 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-270400061

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is a high-severity Android SoC kernel-driver flaw in PowerVR graphics code. A local app could potentially gain higher privileges without user interaction. The public sources do not identify exact phone models or confirm active exploitation.

Executive priority

Treat this as a patch-priority Android fleet issue, especially for managed devices with app-install exposure. Urgency is high, but current sources do not support emergency active-exploitation language.

Technical view

PVRSRVBridgeChangeSparseMem in the PowerVR kernel driver lacks a size check, enabling integer overflow and possible out-of-bounds heap access. CVSS 3.1 is 7.8: local attack vector, low complexity, low privileges, no user interaction, high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to Android SoC environments using the affected PowerVR kernel driver. The source bundle does not name specific OEMs, chipsets, Android versions beyond “Android SoC,” or device models.

Exploitation context

The CVE describes local escalation of privilege from a low-privileged context with no user interaction. The bundle marks KEV as false and provides no cited evidence of active exploitation or public exploit availability.

Researcher notes

The key evidence is the Android bulletin and CVE metadata. Missing details include exact affected PowerVR driver versions, OEM device mapping, and vendor-specific remediation notes. Avoid assuming broader Linux or non-Android exposure from these sources alone.

Mitigation direction

  • Review the Android April 2023 security bulletin for CVE-2021-0875 guidance.
  • Apply OEM or Android security updates covering the affected SoC driver.
  • Prioritize devices with PowerVR GPU kernel drivers in patch planning.
  • Restrict installation of untrusted Android apps while patch status is unresolved.
  • Check vendor advisories for device-specific fixes and support status.

Validation and detection

  • Inventory Android devices and SoCs that may use PowerVR graphics drivers.
  • Confirm device patch levels include the relevant April 2023 Android security fixes.
  • Check OEM release notes for CVE-2021-0875 or Android ID A-270400061.
  • Track unsupported devices as residual local privilege-escalation risk.
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-0875 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-0875Attack 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.