CVE-2026-54872

Range taken from the CVE record, check it before committing. make newentry in security/vuxml creates the vid.

  <vuln vid="FIXME (make newentry)">
    <topic>FIXME -- FIXME</topic>
    <affects>
      <package>
	<name>linux-c7-openssl-devel</name>
	<range><lt>1.0.2zs</lt></range>
      </package>
      <package>
	<name>openssl-unsafe</name>
	<range><lt>1.0.2zs</lt></range>
      </package>
    </affects>
    <description>
      <body xmlns="http://www.w3.org/1999/xhtml">
	<p>Issue summary: The generic elliptic-curve scalar multiplication used
	for
ECDSA and SM2 signature operations with curves that do not have a
	dedicated
implementation leaks information about the secret nonce
	through timing.

Impact summary: An attacker able to measure signing
	times may learn
information about the per-signature secret nonce,
	which over many signatures
can, via a lattice / Hidden Number Problem
	attack, lead to recovery of the
private key.

CWE: CWE-208: Observable
	Timing Discrepancy

Description: The generic elliptic-curve scalar
	multiplication used for
curves that do not have a dedicated
	constant-time implementation pads the
secret scalar with
	non-constant-time BIGNUM operations, so the time taken
depends on the
	value of the secret scalar derived from the ECDSA and SM2 nonce.

The
	leak is very small; observing it requires a large number
	of
measurements. The effect is largest for curves whose group order
	lies
on a machine-word boundary, such as
	brainpoolP384r1.

Applications using ECDSA signing over the Brainpool
	and other generic prime
curves, and SM2 signing on platforms that use
	the generic implementation,
are vulnerable to this issue.

The NIST
	curves P-256, P-384 and P-521 use dedicated
	constant-time
implementations and are not affected.

FIPS Impact:
	no
The FIPS modules are not affected: the approved NIST curves used in
	the FIPS
provider have dedicated constant-time implementations and do
	not use the
affected code path.</p>
      </body>
    </description>
    <references>
      <cvename>CVE-2026-54872</cvename>
      <url>https://nvd.nist.gov/vuln/detail/CVE-2026-54872</url>
    </references>
    <dates>
      <discovery>2026-09-29</discovery>
      <entry>2026-10-25</entry>
    </dates>
  </vuln>