Security readout for executives and security teams
Plain-English summary
This CVE describes a Huawei GPU module permission-check weakness. If successfully exploited, it could affect confidentiality, integrity, and availability on affected HarmonyOS and EMUI versions. The public sources do not provide severity scoring, exploit details, or confirmation of active exploitation.
Executive priority
Prioritize inventory first. If affected Huawei devices are present, route them through normal mobile-device patch governance. Escalate only if Huawei guidance, telemetry, or later intelligence indicates exploitation or higher severity.
Technical view
Huawei reports incomplete read and write permission verification in the GPU module. The listed affected products are HarmonyOS 2.0.0 and EMUI 12.0.0. The CVE maps to CWE-200, but the description also notes possible integrity and availability impact.
Likely exposure
Exposure is most likely limited to Huawei devices running HarmonyOS 2.0.0 or EMUI 12.0.0. Organizations without Huawei endpoint, mobile, or embedded-device use are unlikely to be directly exposed based on the provided sources.
Exploitation context
CISA KEV status is false, and the supplied sources do not state active exploitation, public exploit availability, attacker prerequisites, or required user interaction. Treat exploitability as unconfirmed from this bundle.
Researcher notes
The source bundle is sparse: no CVSS, no fixed builds, no exploit prerequisites, and no detailed GPU module behavior. Avoid assuming broader Huawei product exposure beyond HarmonyOS 2.0.0 and EMUI 12.0.0.
Mitigation direction
- Inventory Huawei devices and identify HarmonyOS or EMUI versions in use.
- Review Huawei July 2023 security bulletin guidance for affected devices.
- Apply Huawei-provided security updates where available for affected products.
- Restrict sensitive workloads on unpatched affected Huawei devices.
- Monitor Huawei advisories for fixed-version or workaround details.
Validation and detection
- Confirm whether any managed devices run HarmonyOS 2.0.0 or EMUI 12.0.0.
- Compare device patch levels against Huawei July 2023 bulletin entries.
- Check MDM or asset records for Huawei mobile or embedded devices.
- Document unsupported, unmanaged, or unpatchable affected devices for risk review.
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-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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-46891 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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 and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
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.
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.