Description of the patch:
This update for leancrypto fixes the following issues
Security issue:
- CVE-2026-34610: The leancrypto library is a cryptographic library that exclusively contains only PQC-resistant
cryptographic algorithms. Prior to version 1.7.1, lc_x509_extract_name_segment() casts size_t vlen to uint8_t when
stori (bsc#1261382).
Non security issues:
- gnutls Illegal instruction lc_kyber_768_kem_dec_selftest (bsc#1253654).
- gnutls: test pqc-hybrid-kx fails on Nehalem or older CPU (bsc#1254370).
Changes for leancrypto:
- Calculate the FIPS HMAC for the leancrypto and the leancrypto-fips
libraries. (bsc#1262399)
- Fix build on kernel 7.0
- Pick fix for ABI issue in AVX2 assembly for Curve448 causing
test failures when building with GCC 16.
- Update to 1.7.2:
- Fix RDSEED counter
- Process code by AI code checkers and apply suggested cosmetic fixes
- Heap memory: always munlock all mlock'ed memory
- Fix ChaCha20 on Apple compiled with XCode 26.4
- Fix a potential crasher with Base64 and applied various fixes reported
- Add X.509 certificate signing request (CSR) generator and parser
- ML-DSA: add lc_dilithium_pk_from_sk API to derive the PK from a given SK
- SLH-DSA: add lc_sphincs_pk_from_sk API to derive the PK from a given SK
- ML-KEM: add lc_kyber_pk_from_sk API to derive the PK from a given SK
- AES-CT: fix non-aligned data processing - reported
- Apply suggestions from Claude code
- X.509: Enforce path length restriction
- Offer a means to select the AES-C constant time / S-Box implementation via
lc_init API
- use the AES-C constant time implementation by default - it is about 3 times
slower than the AES-C S-Box implementation, but more secure. As the
leancrypto library is about secure by default, the CT implementation is
just right. Furthermore, if a caller wants to have the faster AES-C S-Box,
he can call lc_init(LC_INIT_AES_SBOX) at the beginning.
- FIPS: mark only seeded DRBG instances as...