Bug 2376428 (CVE-2025-49600) - CVE-2025-49600 mbedtls: MbedTLS LMS Signature Forgery via Fault Injection
Summary: CVE-2025-49600 mbedtls: MbedTLS LMS Signature Forgery via Fault Injection
Keywords:
Status: NEW
Alias: CVE-2025-49600
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2376712 2376715 2376711 2376713 2376714 2382562
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-07-04 15:01 UTC by OSIDB Bzimport
Modified: 2025-07-22 07:14 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-07-04 15:01:36 UTC
In MbedTLS 3.3.0 before 3.6.4, mbedtls_lms_verify may accept invalid signatures if hash computation fails and internal errors go unchecked, enabling LMS (Leighton-Micali Signature) forgery in a fault scenario. Specifically, unchecked return values in mbedtls_lms_verify allow an attacker (who can induce a hardware hash accelerator fault) to bypass LMS signature verification by reusing stale stack data, resulting in acceptance of an invalid signature. In mbedtls_lms_verify, the return values of the internal Merkle tree functions create_merkle_leaf_value and create_merkle_internal_value are not checked. These functions return an integer that indicates whether the call succeeded or not. If a failure occurs, the output buffer (Tc_candidate_root_node) may remain uninitialized, and the result of the signature verification is unpredictable. When the software implementation of SHA-256 is used, these functions will not fail. However, with hardware-accelerated hashing, an attacker could use fault injection against the accelerator to bypass verification.


Note You need to log in before you can comment on or make changes to this bug.