p PatchFirst

CVE-2025-9231

CVE-2025-9231 · Timing side-channel in SM2 algorithm on 64 bit ARM

This page contains facts from public vulnerability sources. Check the original advisory before updating.

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.

CVSS 6.5 · Medium · EPSS 2.2% · Fix available

Published
Updated

Stack: system · network

Affected products and versions

  • openssl

    Versions
    • ≥ 3.5.0, < 3.5.4: Affected (semver)
    • ≥ 3.4.0, < 3.4.3: Affected (semver)
    • ≥ 3.3.0, < 3.3.5: Affected (semver)
    • ≥ 3.2.0, < 3.2.6: Affected (semver)

    Update to 3.2.6; Update to 3.3.5; Update to 3.4.3; Update to 3.5.4

  • openssl Debian:13

    Versions
    • 3.5.1-1
    Affected ranges
    • ECOSYSTEM: < 3.5.1-1+deb13u1

    Update to 3.5.1-1+deb13u1

  • openssl Debian:14

    Versions
    • 3.5.1-1
    • 3.5.2-1
    • 3.5.3-1
    • 3.5.4-1~deb13u1
    • 3.5.4-1~deb13u2
    Affected ranges
    • ECOSYSTEM: < 3.5.4-1

    Update to 3.5.4-1

  • nodejs Ubuntu:Pro:16.04:LTS

    Versions
    • 0.10.25~dfsg2-2ubuntu1
    • 4.2.2~dfsg-1
    • 4.2.3~dfsg-1
    • 4.2.4~dfsg-1ubuntu1
    • 4.2.4~dfsg-2
    • 4.2.6~dfsg-1ubuntu1
    • 4.2.6~dfsg-1ubuntu4
    • 4.2.6~dfsg-1ubuntu4.1
    • 4.2.6~dfsg-1ubuntu4.2
    • 4.2.6~dfsg-1ubuntu4.2+esm1
    • 4.2.6~dfsg-1ubuntu4.2+esm2
    • 4.2.6~dfsg-1ubuntu4.2+esm3
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • nodejs Ubuntu:Pro:18.04:LTS

    Versions
    • 6.11.4~dfsg-1ubuntu1
    • 6.11.4~dfsg-1ubuntu2
    • 6.12.0~dfsg-1ubuntu1
    • 6.12.0~dfsg-2ubuntu1
    • 6.12.0~dfsg-2ubuntu2
    • 8.10.0~dfsg-2
    • 8.10.0~dfsg-2ubuntu0.2
    • 8.10.0~dfsg-2ubuntu0.3
    • 8.10.0~dfsg-2ubuntu0.4
    • 8.10.0~dfsg-2ubuntu0.4+esm1
    • 8.10.0~dfsg-2ubuntu0.4+esm2
    • 8.10.0~dfsg-2ubuntu0.4+esm3
    • 8.10.0~dfsg-2ubuntu0.4+esm4
    • 8.10.0~dfsg-2ubuntu0.4+esm5
    • 8.10.0~dfsg-2ubuntu0.4+esm6
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • nodejs Ubuntu:Pro:22.04:LTS

    Versions
    • 12.22.5~dfsg-5ubuntu1
    • 12.22.7~dfsg-2ubuntu1
    • 12.22.7~dfsg-2ubuntu3
    • 12.22.9~dfsg-1ubuntu2
    • 12.22.9~dfsg-1ubuntu3
    • 12.22.9~dfsg-1ubuntu3.1
    • 12.22.9~dfsg-1ubuntu3.2
    • 12.22.9~dfsg-1ubuntu3.3
    • 12.22.9~dfsg-1ubuntu3.4
    • 12.22.9~dfsg-1ubuntu3.5
    • 12.22.9~dfsg-1ubuntu3.6
    • 12.22.9~dfsg-1ubuntu3.6+esm2
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • openssl Ubuntu:25.10

    Versions
    • 3.4.1-1ubuntu3
    • 3.5.0-2ubuntu1
    • 3.5.2-1ubuntu1
    Affected ranges
    • ECOSYSTEM: < 3.5.3-1ubuntu2

    Update to 3.5.3-1ubuntu2

  • openssl Ubuntu:26.04:LTS

    Affected ranges
    • ECOSYSTEM: < 3.5.3-1ubuntu2

    Update to 3.5.3-1ubuntu2

Original sources

Check your server →