cve.bz

CVE-2025-47917 arm mbed tls: Use After Free

9.8 criticalExploitEPSS 2.4%

Critical (9.8) in arm mbed tls. EPSS 2.4% estimated probability of exploitation activity in the next 30 days.

On this page
Mbed TLS before 3.6.4 allows a use-after-free in certain situations of applications that are developed in accordance with the documentation. The function mbedtls_x509_string_to_names() takes a head argument that is documented as an output argument. The documentation does not suggest that the function will free that pointer; however, the function does call mbedtls_asn1_free_named_data_list() on that argument, which performs a deep free(). As a result, application code that uses this function (relying only on documented behavior) is likely to still hold pointers to the memory blocks that were freed, resulting in a high risk of use-after-free or double-free. In particular, the two sample programs x509/cert_write and x509/cert_req are affected (use-after-free if the san string contains more than one DN).

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
2.4% (unchanged from 2.4% a week ago; 2.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 85th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2025-07-22. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-416 Use After Free
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-47917 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-47917?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-47917?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-47917 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
mbedtlsbefore 3.6.4

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian11mbedtls2.16.9-0.1+deb11u2DLA-4274-1
Debian11mbedtls2.16.9-0.1+deb11u3DLA-4274-2
Debian12mbedtlsno fix listedDEBIAN-CVE-2025-47917
Debian13, 14mbedtls3.6.4-1DEBIAN-CVE-2025-47917
Ubuntu16.04:LTS, 25.10mbedtlsno fix listedUBUNTU-CVE-2025-47917
UbuntuPro:18.04:LTSmbedtls2.8.0-1ubuntu0.1~esm1UBUNTU-CVE-2025-47917 USN-8123-1
UbuntuPro:20.04:LTSmbedtls2.16.4-1ubuntu2+esm1UBUNTU-CVE-2025-47917 USN-8123-1
UbuntuPro:22.04:LTSmbedtls2.28.0-1ubuntu0.1~esm1UBUNTU-CVE-2025-47917 USN-8123-1
UbuntuPro:24.04:LTSmbedtls2.28.8-1ubuntu0.1~esm1UBUNTU-CVE-2025-47917 USN-8123-1
openSUSELeap 16.0mbedtls3.6.6-bp160.1.1openSUSE-SU-2026:21144-1
Alpinev3.20, v3.21, v3.22 and 1 morembedtls3.6.4-r0ALPINE-CVE-2025-47917
Alpinev3.24mbedtls, mbedtls33.6.4-r0ALPINE-CVE-2025-47917

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpine.

Public exploits

References

Check your stackJSON