Cyber Resilience

CVE-2026-24930

Memory Safety in Huawei Harmonyos 5.1.0 … 6.0.0

Memory SafetyRace Condition
Published
06 February 2026
Modified
09 February 2026
Patch / advisory
View advisory
CVSS Score v3.1 8.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.00066 0.0th percentile
Risk Priority 57 floored blend · peak EPSS

Summary

CVE-2026-24930 is a high-severity Race Condition (CWE-362) vulnerability in Huawei Harmonyos. Its CVSS base score is 8.4 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Client Execution (T1203); ranked at the 0.0th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-24930 is a Use-After-Free (UAF) concurrency vulnerability, associated with CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization) and CWE-416 (Use After Free), affecting the graphics module in Huawei consumer products. Published on 2026-02-06, it carries a CVSS v3.1 base score of 8.4 (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), indicating high severity with potential impacts across confidentiality, integrity, and availability.

A local attacker can exploit this vulnerability with low complexity, requiring no privileges or user interaction. Successful exploitation may allow the attacker to achieve high-impact effects, including unauthorized access to sensitive data, modification of system integrity, and disruption of availability, such as through arbitrary code execution or system crashes in the graphics subsystem.

Huawei has issued security bulletins addressing this issue, available at https://consumer.huawei.com/en/support/bulletin/2026/2/ and https://consumer.huawei.com/en/support/bulletinlaptops/2026/2/, which detail recommended patches and mitigation steps for affected consumer devices and laptops.

OWASP Top 10 for Web (2025)

A06:2025 Insecure Design

EU & UK References

Vulnerability Data

UAF concurrency vulnerability in the graphics module. Impact: Successful exploitation of this vulnerability may affect availability.

CWE(s)
CWE-362CWE-416

Related Threats

MITRE ATT&CK Enterprise Techniques

T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-58303Same product: Huawei Harmonyos
CVE-2023-52115Same product: Huawei Harmonyos
CVE-2025-54635Same product: Huawei Harmonyos
CVE-2025-58299Same product: Huawei Harmonyos
CVE-2026-24914Same product: Huawei Harmonyos
CVE-2023-44095Same product: Huawei Harmonyos
CVE-2024-57959Same product: Huawei Harmonyos
CVE-2023-46769Same product: Huawei Harmonyos
CVE-2026-24927Same product: Huawei Harmonyos
CVE-2026-34859Same product: Huawei Harmonyos

Affected Assets

huawei
harmonyos
5.1.0, 6.0.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 3 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V10.4.2
  • V10.4.5
  • V15.1.3
  • V15.4.1

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover use-after-free bugs through dynamic analysis or fuzzing.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles can require memory-safe constructs or languages that structurally avoid introducing use-after-free.

SC-39 Process Isolation partial match

Maintaining separate execution domains for each process structurally eliminates unintended concurrent access to the same shared resources.

SC-4 Information in Shared System Resources partial match

Preventing unintended information transfer through shared system resources directly addresses the improper concurrent modification that defines a race condition.

SI-16 Memory Protection partial match

Memory protection controls limit exploitation impact by blocking unauthorized code execution from dangling pointers.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper synchronization primitives and concurrency testing that prevent race conditions.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover use-after-free issues via scanning or analysis but do not prevent their introduction.

PR.PS-02 partial match
prevents

Routine patching removes known use-after-free instances after they have been introduced in released software.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect race conditions, but does not prevent them at design or coding time.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates concurrency controls and synchronization primitives that directly prevent race conditions.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify thread-safety and locking rules, but do not prescribe implementation details.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles require proper synchronization and resource isolation, addressing the root cause of CWE-362.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid unsafe concurrent access patterns and mandate atomic operations or locks.

A.8.32 Change management partial match
prevents

Change-management processes help ensure memory-safety fixes are deployed consistently.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (1 rule)
  • V-248592 OL 8 must clear memory when it is freed to prevent use-after-free attacks. prevents CWE-416
RHEL 8 (1 rule)
  • V-230279 RHEL 8 must clear memory when it is freed to prevent use-after-free attacks. prevents CWE-416
RHEL 9 (1 rule)
  • V-257794 RHEL 9 must clear memory when it is freed to prevent use-after-free attacks. prevents CWE-416

References