Timing side-channel in SM2 algorithm on 64 bit ARM
CVE-2025-9231 is fixed in 15 products on 1 platform, first by libssl3t64 3.5.3-1ubuntu2, released September 29, 2025. It is not reported as exploited. Patch Radar priority: Routine.
Issue summary: A timing side-channel which could potentially allow remoterecovery of the private key exists in the SM2 algorithm implementation on64 bitARM platforms.Impact summary: A timing side-channel in SM2 signature computations on 64bitARM 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 anattack.OpenSSL does not directly support certificates with SM2 keys in TLS, and sothis CVE is not relevant in most TLS contexts. However, given that it ispossible to add support for such certificates via a custom provider,coupledwith the fact that in such a custom provider context the private key may berecoverable via remote timing measurements, we consider this to be aModerateseverity issue.The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected bythisissue, as SM2 is not an approved algorithm.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| libssl3t64 · Ubuntu 25.04 (plucky) | 3.4.1-1ubuntu4 | libssl3t64 3.4.1-1ubuntu4 | Sep 30, 2025 |
| libssl3t64 · Ubuntu 25.10 (questing) | 3.5.3-1ubuntu2 | libssl3t64 3.5.3-1ubuntu2 | Sep 29, 2025 |
| libssl3t64 · Ubuntu 26.04.1 LTS (resolute) | 3.5.3-1ubuntu2 | libssl3t64 3.5.3-1ubuntu2 | Sep 29, 2025 |
| nodejs24 · sles 15.7 | 24.18.1-150700.15.18.1 | SUSE-SU-2026:3835-1 | Sep 10, 2026 |
| openssl · Debian 13.5 (trixie) | 3.5.1-1+deb13u1 | DEBIAN-CVE-2025-9231 | Sep 30, 2025 |
| openssl · Debian 14 | 3.5.4-1 | DEBIAN-CVE-2025-9231 | Sep 30, 2025 |
| openssl · Ubuntu 25.04 (plucky) | 3.4.1-1ubuntu4 | openssl 3.4.1-1ubuntu4 | Sep 30, 2025 |
| openssl · Ubuntu 25.10 (questing) | 3.5.3-1ubuntu2 | openssl 3.5.3-1ubuntu2 | Sep 29, 2025 |
| openssl · Ubuntu 26.04.1 LTS (resolute) | 3.5.3-1ubuntu2 | openssl 3.5.3-1ubuntu2 | Sep 29, 2025 |
| openssl · amzn 2023 | 1:3.2.2-1.amzn2023.0.2 | ALAS2023-2025-1225 | Oct 14, 2025 |
| openssl · sles 15.7 | 3.5.0-150700.3.4.1 | SUSE-SU-2026:3835-1 | Sep 10, 2026 |
| openssl-3 · opensuse-leap 16.0 | 3.5.0-160000.4.1 | OPENSUSE-SU-2025:20164-1 | Dec 15, 2025 |
| openssl-3 · sles 15.7 | 3.5.0-150700.5.45.2 | SUSE-SU-2026:3835-1 | Sep 10, 2026 |
| openssl-3 · sles 16.0 | 3.5.0-160000.4.1 | SUSE-SU-2025:21213-1 | Dec 15, 2025 |
| openssl-debuginfo · amzn 2023 | 1:3.2.2-1.amzn2023.0.2 | ALAS2023-2025-1225 | Oct 14, 2025 |
| openssl-debugsource · amzn 2023 | 1:3.2.2-1.amzn2023.0.2 | ALAS2023-2025-1225 | Oct 14, 2025 |
| openssl-devel · amzn 2023 | 1:3.2.2-1.amzn2023.0.2 | ALAS2023-2025-1225 | Oct 14, 2025 |
| openssl-fips-provider-latest · amzn 2023 | 1:3.2.2-1.amzn2023.0.2 | ALAS2023-2025-1225 | Oct 14, 2025 |
| openssl-fips-provider-latest-debuginfo · amzn 2023 | 1:3.2.2-1.amzn2023.0.2 | ALAS2023-2025-1225 | Oct 14, 2025 |
| openssl-libs · amzn 2023 | 1:3.2.2-1.amzn2023.0.2 | ALAS2023-2025-1225 | Oct 14, 2025 |
| openssl-libs-debuginfo · amzn 2023 | 1:3.2.2-1.amzn2023.0.2 | ALAS2023-2025-1225 | Oct 14, 2025 |
| openssl-perl · amzn 2023 | 1:3.2.2-1.amzn2023.0.2 | ALAS2023-2025-1225 | Oct 14, 2025 |
| openssl-provider-legacy · Ubuntu 25.04 (plucky) | 3.4.1-1ubuntu4 | openssl-provider-legacy 3.4.1-1ubuntu4 | Sep 30, 2025 |
| openssl-provider-legacy · Ubuntu 25.10 (questing) | 3.5.3-1ubuntu2 | openssl-provider-legacy 3.5.3-1ubuntu2 | Sep 29, 2025 |
| openssl-provider-legacy · Ubuntu 26.04.1 LTS (resolute) | 3.5.3-1ubuntu2 | openssl-provider-legacy 3.5.3-1ubuntu2 | Sep 29, 2025 |
| openssl-snapsafe-libs · amzn 2023 | 1:3.2.2-1.amzn2023.0.2 | ALAS2023-2025-1225 | Oct 14, 2025 |
| openssl-snapsafe-libs-debuginfo · amzn 2023 | 1:3.2.2-1.amzn2023.0.2 | ALAS2023-2025-1225 | Oct 14, 2025 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.