PT-2025-48529 · Julia · Mbedtls Jll

Published

2025-11-21

·

Updated

2025-11-21

None

No severity ratings or metrics are available. When they are, we'll update the corresponding info on the 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).
Found an issue in the description? Have something to add? Feel free to write us 👾

Related Identifiers

JLSEC-2025-231

Affected Products

Mbedtls Jll