CVE-2025-47917: Use After Free

Published Jul 20, 2025
·
Updated

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 mbedtlsx509stringtonames() 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 mbedtlsasn1freenameddatalist() 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/certwrite and x509/certreq are affected (use-after-free if the san string contains more than one DN).

Affected Software

2 affected components
Arm mbed TLS<3.6.4
Arm mbed TLS<3.6.4

Event History

Jul 20, 2025
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:15 PM
DescriptionSeverityWeaknessAffected Software
Sep 16, 2025
Exploit Published
12:00 AM
Oct 31, 2025
Known Exploited
06:46 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-47917?

CVE-2025-47917 is categorized as a use-after-free vulnerability, which may lead to potential memory corruption issues.

2

How do I fix CVE-2025-47917?

To fix CVE-2025-47917, upgrade Mbed TLS to version 3.6.4 or later.

3

What is the affected software for CVE-2025-47917?

CVE-2025-47917 affects Mbed TLS versions prior to 3.6.4.

4

What specific function is involved in CVE-2025-47917?

The involved function in CVE-2025-47917 is mbedtls_x509_string_to_names(), which improperly handles its head output argument.

5

What can be the consequences of CVE-2025-47917?

The consequences of CVE-2025-47917 may include application crashes or potential exploitation leading to arbitrary code execution.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203