CVE-2025-22866 | Timing sidechannel for P-256 on ppc64le in crypto/internal/nistec

Due to the usage of a variable time instruction in the assembly implementation of an internal function, a small number of bits of secret scalars are leaked on the ppc64le architecture. Due to the way this function is used, we do not believe this leakage is enough to allow recovery of the private key when P-256 is used in any well known protocols.

Published: 2025-02-06 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-22866 is rated Low Risk (17/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.02%). Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-22866

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-21 0.07% 0.02% -0.06%
2 2025-11-18 0.04% 0.07% +0.03%
3 2025-02-07 — 0.04% —

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-22866

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.0 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.5 1.4 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-22866

OS Trackers for CVE-2025-22866

vendor priority summary link
alpine — CVE-2025-22866: 1 source package rows (go); 3 state rows across 3 repos (3.21-community, 3.22-community, edge-community); fixed 3, open 0. https://security.alpinelinux.org/vuln/CVE-2025-22866
debian not yet assigned CVE-2025-22866 not yet assigned priority: Debian including 3 source packages (golang-1.15, golang-1.19, golang-1.24), 3 status rows across 3 suites (bookworm, bullseye, trixie): open 2, resolved 1. https://security-tracker.debian.org/tracker/CVE-2025-22866
redhat medium — https://access.redhat.com/security/cve/CVE-2025-22866
suse medium CVE-2025-22866 severity moderate: SUSE including 88 source package names (1.23.10-2.7.6:go1.23-1.23.6-150000.1.21.1, 1.23.10-2.7.6:go1.23-doc-1.23.6-150000.1.21.1, …), 446 product×package rows across 48 product lines (Container bci/golang, Container suse/sl-micro/6.0/baremetal-os-container, … (48 product lines)): Fixed 406, Known Not Affected 40. https://www.suse.com/security/cve/CVE-2025-22866/
ubuntu medium CVE-2025-22866 medium priority: Ubuntu including 15 source packages (golang, golang-1.10, …), 116 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 65, needs-triage 38, ignored 10, released 3. https://ubuntu.com/security/CVE-2025-22866

Affected software / configurations for CVE-2025-22866

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-22866

cvelogic Threat Intelligence