Security readout for executives and security teams
Plain-English summary
CVE-2021-22350 affects Huawei smartphones running listed EMUI and Magic UI versions. The documented impact is device crash and restart, which is primarily an availability issue. The source bundle does not provide severity, CVSS, attack vector, or proof of active exploitation.
Executive priority
Treat this as a targeted mobile hygiene item, not an emergency, based on current evidence. Prioritize if the organization has Huawei mobile devices in sensitive workflows or unmanaged BYOD access.
Technical view
The CVE describes a memory buffer improper operation limit vulnerability in EMUI 11.0.0/10.1.1 and Magic UI 4.0.0/3.1.1. Successful exploitation may crash and restart the device. Public details do not identify the vulnerable component, required privileges, or exploit path.
Likely exposure
Exposure is limited to Huawei smartphones running the affected EMUI or Magic UI versions. Enterprise risk depends on whether managed or BYOD devices remain on those builds and whether Huawei security updates were applied.
Exploitation context
CISA KEV status is false, and the provided sources do not report active exploitation. The available public record does not state whether exploitation is remote, local, user-assisted, or requires privileges.
Researcher notes
Evidence is sparse. The CVE record names affected UI versions and impact but omits CVSS, CWE, component, attack vector, and prerequisites. Avoid assuming broader Huawei product exposure beyond EMUI and Magic UI versions listed.
Mitigation direction
- Inventory Huawei devices running affected EMUI or Magic UI versions.
- Review Huawei's May 2021 security bulletin for official update guidance.
- Apply vendor-provided security updates where available.
- Restrict access for unmanaged or outdated mobile devices.
- Monitor mobile device crashes or restart patterns.
Validation and detection
- Confirm device OS versions through MDM or endpoint inventory.
- Check whether Huawei May 2021 security updates are installed.
- Identify unmanaged BYOD devices matching affected versions.
- Review helpdesk or MDM telemetry for crash and restart spikes.
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.
CVE-2021-22350 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
- CVE List V5 sourceCVE List V5
- https://consumer.huawei.com/en/support/bulletin/2021/5/CVE reference · x_refsource_MISC
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.