CVE-2021-36987
CVE-2021-36987 is a medium-severity vulnerability in Huawei Emui with a CVSS 3.x base score of 5.9. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-362.
Key facts
- Severity: Medium (CVSS 3.x base score 5.9)
- CVSS v2: 7.1
- EPSS exploit prediction: 0% (37th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-362
- Affected product: Huawei Emui
- Published:
- Last modified:
Description
There is a issue that nodes in the linked list being freed for multiple times in Huawei Smartphone due to race conditions. Successful exploitation of this vulnerability can cause the system to restart.
Frequently asked questions
- What is CVE-2021-36987?
- There is a issue that nodes in the linked list being freed for multiple times in Huawei Smartphone due to race conditions. Successful exploitation of this vulnerability can cause the system to restart.
- How severe is CVE-2021-36987?
- CVE-2021-36987 has a CVSS 3.x base score of 5.9, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
- Is CVE-2021-36987 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (37th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2021-36987?
- CVE-2021-36987 primarily affects Huawei Emui. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
- How do I fix CVE-2021-36987?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- When was CVE-2021-36987 published?
- CVE-2021-36987 was published on 2021-10-28 and last updated on 2026-06-17.
References
Affected products (4)
- cpe:2.3:o:huawei:emui:10.1.1:*:*:*:*:*:*:*
- cpe:2.3:o:huawei:emui:11.0.0:*:*:*:*:*:*:*
- cpe:2.3:o:huawei:magic_ui:3.1.1:*:*:*:*:*:*:*
- cpe:2.3:o:huawei:magic_ui:4.0.0:*:*:*:*:*:*:*
More vulnerabilities in Huawei Emui
- CVE-2023-52381 — Critical (CVSS 9.8): Script injection vulnerability in the email module.Successful exploitation of this vulnerability may affect service…
- CVE-2023-52378 — Critical (CVSS 9.8): Vulnerability of incorrect service logic in the WindowManagerServices module.Successful exploitation of this…
- CVE-2023-52370 — Critical (CVSS 9.8): Stack overflow vulnerability in the network acceleration module.Successful exploitation of this vulnerability may cause…
- CVE-2023-52103 — Critical (CVSS 9.8): Buffer overflow vulnerability in the FLP module. Successful exploitation of this vulnerability may cause out-of-bounds…
- CVE-2023-46773 — Critical (CVSS 9.8): Permission management vulnerability in the PMS module. Successful exploitation of this vulnerability may cause…
- CVE-2023-44116 — Critical (CVSS 9.8): Vulnerability of access permissions not being strictly verified in the APPWidget module.Successful exploitation of this…
All CVEs affecting Huawei Emui →
Other CWE-362 (Race Condition) vulnerabilities
- CVE-2022-27626 — Critical (CVSS 10.0): A vulnerability regarding concurrent execution using shared resource with improper synchronization ('Race Condition')…
- CVE-2015-8556 — Critical (CVSS 10.0): Local privilege escalation vulnerability in the Gentoo QEMU package before 2.5.0-r1.
- CVE-2014-0703 — Critical (CVSS 10.0): Cisco Wireless LAN Controller (WLC) devices 7.4 before 7.4.110.0 distribute Aironet IOS software with a race condition…
- CVE-2010-1228 — Critical (CVSS 10.0): Multiple race conditions in the sandbox infrastructure in Google Chrome before 4.1.249.1036 have unspecified impact and…
- CVE-2008-6598 — Critical (CVSS 10.0): Multiple race conditions in WANPIPE before 3.3.6 have unknown impact and attack vectors related to "bri restart logic."
- CVE-2026-46137 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: ADD_ADDR rtx: fix potential…