CVE-2025-9231: Timing side-channel in SM2 algorithm on 64 bit ARM
Issue summary: A timing side-channel which could potentially allow remote recovery of the private key exists in the SM2 algorithm implementation on 64 bit ARM platforms.
Impact summary: A timing side-channel in SM2 signature computations on 64 bit ARM platforms could allow recovering the private key by an attacker..
While remote key recovery over a network was not attempted by the reporter, timing measurements revealed a timing signal which may allow such an attack.
OpenSSL does not directly support certificates with SM2 keys in TLS, and so this CVE is not relevant in most TLS contexts. However, given that it is possible to add support for such certificates via a custom provider, coupled with the fact that in such a custom provider context the private key may be recoverable via remote timing measurements, we consider this to be a Moderate severity issue.
The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as SM2 is not an approved algorithm.
Other sources
Timing side-channel in SM2 algorithm on 64 bit ARM
— Microsoft
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-9231?
CVE-2025-9231 has a high severity rating due to its potential to allow remote recovery of private keys through a timing side-channel.
How do I fix CVE-2025-9231?
To fix CVE-2025-9231, update to a patched version of OpenSSL that addresses vulnerabilities in the SM2 algorithm.
Which versions of OpenSSL are affected by CVE-2025-9231?
CVE-2025-9231 affects all versions of OpenSSL prior to 3.6 on 64 bit ARM platforms.
What impact does CVE-2025-9231 have on my system?
CVE-2025-9231 could allow attackers to recover private keys, compromising the security of encrypted communications.
Is there a workaround for CVE-2025-9231?
There are no effective workarounds for CVE-2025-9231; therefore, upgrading to a fixed version is strongly recommended.