CVE-2025-9231

Timing side-channel in SM2 algorithm on 64 bit ARM

MEDIUM
6.5
CVSS Score
Published: September 30, 2025 at 01:17 PM UTC
Updated: July 14, 2026 at 01:37 PM UTC
15 products affected across 2 vendorsOpenSSLRUGGEDCOM RST2428P FirmwareSIMATIC CN 4100

Using OpenSSL by OpenSSL?

Get instant alerts when new vulnerabilities affect OpenSSL - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.5
Exploit prediction
EPSS 2%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.2.0 ≤ v < 3.2.63.3.0 ≤ v < 3.3.53.4.0 ≤ v < 3.4.33.5.0 ≤ v < 3.5.43.2.03.3.03.4.03.5.0
Affected range stops below 3.2.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.3.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.4.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.5.4, so it looks safe — our inference, not a vendor statement
v < V3.3v < V4.0
Affected range stops below V3.3, so it looks safe — our inference, not a vendor statement
Affected range stops below V4.0, so it looks safe — our inference, not a vendor statement
v < V3.3
Affected range stops below V3.3, so it looks safe — our inference, not a vendor statement
v < V3.3
Affected range stops below V3.3, so it looks safe — our inference, not a vendor statement
v < V3.3
Affected range stops below V3.3, so it looks safe — our inference, not a vendor statement
v < V3.3
Affected range stops below V3.3, so it looks safe — our inference, not a vendor statement
v < V3.3
Affected range stops below V3.3, so it looks safe — our inference, not a vendor statement
v < V3.3
Affected range stops below V3.3, so it looks safe — our inference, not a vendor statement
v < V3.3
Affected range stops below V3.3, so it looks safe — our inference, not a vendor statement
v < V3.3
Affected range stops below V3.3, so it looks safe — our inference, not a vendor statement

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

6.5MEDIUMCISA-ADP
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
LOW
Integrity
NONE
Availability
LOW
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-385

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card