NVD / CVE Program· CNA huawei

CVE-2025-58311: UAF vulnerability in the USB driver module.

HighCVSS 7.1 · v3.1—No exploit No fix recorded

Noroxi assessment

Priority: Monitor (action score 28/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.08% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

UAF vulnerability in the USB driver module. Impact: Successful exploitation of this vulnerability will affect availability and confidentiality.

Memory safety

BDU:2025-15155

Published: Nov 28, 2025
Updated: Oct 18, 2026
EPSS: 0.0% · 0th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 28 / 40 · 7.1 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.0%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 7.1
CNA · huawei: 5.8; 1.3 point gap

CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
huawei	emui	cpe:2.3:o:huawei:emui
huawei	harmonyos	cpe:2.3:o:huawei:harmonyos

Versions reported by the vendor

Affected version ranges reported by the assigning authority (huawei). Independent of NVD's CPE analysis and usually ahead of it.

Huawei EMUI
- 15.0.0, 14.2.0, 14.0.0affected
Huawei HarmonyOS
- 5.1.0, 5.0.1, 4.3.1, 4.3.0, 4.2.0, 4.0.0affected

Affected versions · NVD (9)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

huawei emui14.0.0
huawei emui14.2.0
huawei emui15.0.0
huawei harmonyos4.0.0
huawei harmonyos4.2.0
huawei harmonyos4.3.0
huawei harmonyos4.3.1
huawei harmonyos5.0.1
huawei harmonyos5.1.0

Same product

huawei: all records

Other highest-scoring records for the same primary product.

CVE-2024-57961Out-of-bounds write vulnerability in the emcom module Impact: Successful exploitation of this vulnerability may cause features to perform…
39Monitor
CVE-2024-57959Use-After-Free (UAF) vulnerability in the display module Impact: Successful exploitation of this vulnerability may cause features to…
39Monitor
CVE-2024-32991Permission verification vulnerability in the wpa_supplicant module Impact: Successful exploitation of this vulnerability will affect…
39Monitor

Published before and after this one in the same product

← EarlierCVE-2025-58314Nov 28, 2025 · Vulnerability of accessing invalid memory in the component driver module.
28Monitor
← EarlierCVE-2025-58302Nov 28, 2025 · Permission control vulnerability in the Settings module.
22Monitor
Later →CVE-2025-66325Dec 8, 2025 · Permission control vulnerability in the package management module.
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2024-57959295 days apartUse-After-Free (UAF) vulnerability in the display module Impact: Successful exploitation of this vulnerability may cause features to…
39Monitor
CVE-2024-56434325 days apartUAF vulnerability in the device node access module Impact: Successful exploitation of this vulnerability may cause service exceptions of…
30Monitor
CVE-2024-39672491 days apartMemory request logic vulnerability in the memory module.
28Monitor
CVE-2026-2491770 days apartUAF vulnerability in the security module.
22Monitor
CVE-2026-2492770 days apartOut-of-bounds access vulnerability in the frequency modulation module.
22Monitor
CVE-2025-53185145 days apartVirtual address reuse issue in the memory management module, which can be exploited by non-privileged users to access released…
22Monitor

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: none
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: None
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log (0)

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

consumer.huawei.com/en/support/bulletin/2025/11/

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records