Answer in brief
CVE-2025-9231 records a Medium severity (CVSS 6.5) vulnerability in Timing side-channel in SM2 algorithm on 64 bit ARM. The current sources do not mark it as known exploited. The current feed maps OpenSSL/OpenSSL (generic), Siemens/RUGGEDCOM RST2428P (generic), Siemens/RUGGEDCOM RST2428P (generic), Siemens/SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps OpenSSL/OpenSSL (generic), Siemens/RUGGEDCOM RST2428P (generic), Siemens/RUGGEDCOM RST2428P (generic), Siemens/SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| OpenSSL/OpenSSLgeneric | >=3.5.0 <3.5.4 || >=3.4.0 <3.4.3 || >=3.3.0 <3.3.5 || >=3.2.0 <3.2.6 | 3.5.4, 3.4.3, 3.3.5, 3.2.6 |
| Siemens/RUGGEDCOM RST2428Pgeneric | >=0 <V3.3 | V3.3 |
| Siemens/RUGGEDCOM RST2428Pgeneric | >=0 <V4.0 | V4.0 |
| Siemens/SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 familygeneric | >=0 <V3.3 | V3.3 |
| Siemens/SCALANCE XCH328generic | >=0 <V3.3 | V3.3 |
| Siemens/SCALANCE XCM324generic | >=0 <V3.3 | V3.3 |
| Siemens/SCALANCE XCM328generic | >=0 <V3.3 | V3.3 |
| Siemens/SCALANCE XCM332generic | >=0 <V3.3 | V3.3 |
| Siemens/SCALANCE XRH334 (24 V DC, 8xFO, CC)generic | >=0 <V3.3 | V3.3 |
| Siemens/SCALANCE XRM334 (230 V AC, 12xFO)generic | >=0 <V3.3 | V3.3 |
| Siemens/SCALANCE XRM334 (230V AC, 2x10G, 24xSFP, 8xSFP+)generic | >=0 <V3.3 | V3.3 |
| Siemens/SCALANCE XRM334 (230 V AC, 8xFO)generic | >=0 <V3.3 | V3.3 |
| Siemens/SCALANCE XRM334 (24 V DC, 12xFO)generic | >=0 <V3.3 | V3.3 |
| Siemens/SCALANCE XRM334 (24V DC, 2x10G, 24xSFP, 8xSFP+)generic | >=0 <V3.3 | V3.3 |
| Siemens/SCALANCE XRM334 (24 V DC, 8xFO)generic | >=0 <V3.3 | V3.3 |
| Siemens/SCALANCE XRM334 (2x230 V AC, 12xFO)generic | >=0 <V3.3 | V3.3 |
| Siemens/SCALANCE XRM334 (2x230V AC, 2x10G, 24xSFP, 8xSFP+)generic | >=0 <V3.3 | V3.3 |
| Siemens/SCALANCE XRM334 (2x230 V AC, 8xFO)generic | >=0 <V3.3 | V3.3 |
| Siemens/SIDIS Secured SmartPluggeneric | >=0 <V7.26.0310 | V7.26.0310 |
| Siemens/SIMATIC CN 4100generic | >=0 <V5.0 | V5.0 |
Published upstream
Sep 30, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 14, 2026
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.
Quoted source text, attributed separately from HOL analysis.