Security readout for executives and security teams
Plain-English summary
This flaw affects Android SoC builds using a PowerVR kernel driver. A malicious local app or process could trigger a driver integer overflow and potentially gain higher device privileges. The business risk is device compromise, not remote internet-wide exploitation.
Executive priority
Treat this as a high-priority mobile fleet patching issue. It is not described as remotely exploitable, but successful exploitation could give an already-present malicious app or process powerful device privileges.
Technical view
PVRSRVBridgePhysmemNewRamBackedLockedPMR in the PowerVR kernel driver lacks a required size check. Sources describe CWE-190 integer overflow leading to possible out-of-bounds heap access and local privilege escalation. CVSS 3.1 is 7.8, with local attack vector, low complexity, low privileges, and no user interaction.
Likely exposure
Exposure is likely limited to Android devices whose SoC/vendor build includes the affected PowerVR kernel driver. The source bundle names Android SoC but does not list specific OEM models, chipsets, or patch levels beyond the Android April 2023 bulletin reference.
Exploitation context
The cited CVE data supports local privilege escalation only. An attacker would need low-privileged local code execution on the device. The bundle says user interaction is not required. KEV is false, and no cited source states active exploitation.
Researcher notes
The source bundle provides the vulnerable function, bug class, Android ID, CVSS vector, and impact, but not affected device families or patch commit details. Avoid assuming specific PowerVR products or exploit availability without vendor confirmation.
Mitigation direction
- Apply OEM Android security updates that include the April 2023 Android bulletin fixes.
- Prioritize Android fleets with PowerVR GPUs or vendor-confirmed affected SoCs.
- Check OEM and SoC vendor advisories for model-specific remediation details.
- Restrict untrusted app installation on devices awaiting updates.
- Retire or isolate devices with no vendor patch path.
Validation and detection
- Inventory Android device models, SoCs, GPU drivers, and current security patch levels.
- Confirm whether OEM bulletins map devices to CVE-2021-0876 or Android ID A-270400229.
- Verify devices have received the relevant April 2023 Android security bulletin fixes.
- Use MDM or EMM reporting to identify lagging patch levels.
- Track exceptions where vendors do not disclose PowerVR driver status.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCVE-2021-0876 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- 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
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://source.android.com/security/bulletin/2023-04-01CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.