openssl/include, branch openssl-3.4.6

Copyright year updates

2026-06-09T12:00:17Z

Reviewed-by: Neil Horman Reviewed-by: Saša Nedvědický MergeDate: Tue Jun 9 12:00:18 2026 Release: yes

QUIC stack must limit the number of PATH_CHALLENGE frames processed in RX

2026-06-08T14:43:06Z

Currently local QUIC stack allocates PATH_RESPONSE frame for every PATH_CHALLENGE frame it receives in single packet from its remote peer. The memory with PATH_RESPONSE frame is released after local QUIC stack receives an ACK which confirms reception of PATH_RESPONSE by remote peer. This gives remote peer too much control over memory resources local QUIC stack may consume. Quoting RFC 9000 section 9.2.1: ...an endpoint SHOULD NOT send multiple PATH_CHALLENGE frames in a single packet. Limiting the number of PATCH_CHALLENGE frames to 1 per QUIC packet received helps to reduce heap memory overhead required to process PATH_CHALLENGE frame. Currently QUIC ACKM (ACK-manager) keeps all frames in retransmission buffer until ACK is received. It can be changed such frames which don't need to be ACKed don't need to be kept in retrans buffer, those can be released right after transmission. Fixes CVE-2026-34183 Reviewed-by: Nikola Pajkovsky Reviewed-by: Neil Horman Reviewed-by: Tomas Mraz MergeDate: Mon Jun 8 14:43:13 2026

CMS: Produce error when AEAD algorithms are used in enveloped data

2026-06-08T14:29:49Z

Fixes GH-21414 Reviewed-by: Matt Caswell Reviewed-by: Tomas Mraz (Merged from https://github.com/openssl/openssl/pull/27772)

Refactor BN_mod() and BN_nnmod() arguments to match documentation

2026-05-29T07:26:00Z

The documentation has this signature for that function: int BN_mod(BIGNUM *r, const BIGNUM *a, const BIGNUM *m, BN_CTX *ctx); int BN_nnmod(BIGNUM *r, const BIGNUM *a, const BIGNUM *m, BN_CTX *ctx); The implementation, however, had this signature: #define BN_mod(rem, m, d, ctx) BN_div(NULL, (rem), (m), (d), (ctx)) int BN_nnmod(BIGNUM *r, const BIGNUM *m, const BIGNUM *d, BN_CTX *ctx); That pattern alone trips up anyone who associates 'm' with modulus, and and finds themselves using BN_nnmod() incorrectly. This change modifies the argument names to match documentation. Reviewed-by: Matt Caswell Reviewed-by: Tomas Mraz Reviewed-by: Igor Ustinov Reviewed-by: Eugene Syromiatnikov MergeDate: Fri May 29 07:26:04 2026 (Merged from https://github.com/openssl/openssl/pull/31304)

Fix ignored call in ossl_rcu_call when cb item alloc fails

2026-05-18T07:21:59Z

Currently when allocation of cb item fails, the actual cb function is not called. The is used just in hashtable when the cb function frees the old item which result in memory leak. To fix this, the allocation needs to be separated and happen before the assign operation is done. Reviewed-by: Tomas Mraz Reviewed-by: Nikola Pajkovsky MergeDate: Mon May 18 07:22:03 2026 (Merged from https://github.com/openssl/openssl/pull/31165)

Make SSL_get_stream_write_state() safe for concluded streams

2026-04-28T12:50:27Z

QUIC stack may panic when application calls SSL_get_stream_write_state() on cocluded QUIC stream onject. The sequence of action which leads to NULL pointer dereference is as follows: - application uses SSL_stream_conclude(ssl_stream, 0) to conclude the stream (let remote peer know no to expect more data) - application uses SSL_get_stream_write_state(ssl_stream) to query stream state. If underlying sstream object is gone by the time when SSL_get_stream_wtite_state() is called, then application may see NULL pointer dereference. The underlying sstream object is freed when FIN sent on beahalf of SSL_stream_conclude() is ACKed by remote peer. Original-PR: https://github.com/openssl/openssl/pull/30913 Original-Commit: 211b564f8631 "Make SSL_get_stream_write_state() safe for concluded streams" Reviewed-by: Eugene Syromiatnikov Reviewed-by: Matt Caswell MergeDate: Tue Apr 28 12:41:10 2026 (Merged from https://github.com/openssl/openssl/pull/30960) (cherry picked from commit 847c8065e9dc09283fdfbe751ec515b16da0a4e9)

Removes duplicated __owur.

2026-04-24T11:04:25Z

Reviewed-by: Nikola Pajkovsky Reviewed-by: Eugene Syromiatnikov MergeDate: Fri Apr 24 11:04:49 2026 (Merged from https://github.com/openssl/openssl/pull/30933)

Copyright year updates

2026-04-07T12:31:52Z

Reviewed-by: Neil Horman Reviewed-by: Eugene Syromiatnikov MergeDate: Tue Apr 7 12:31:53 2026 Release: yes

Apply clang-format to the source tree

2026-04-03T14:50:46Z

Ensure that all the source files are formatted with the current .clang-format configuration, to avoid spurious clang-format checker errors when arbitrary files are touched. Signed-off-by: Eugene Syromiatnikov Reviewed-by: Nikola Pajkovsky Reviewed-by: Neil Horman Reviewed-by: Tomas Mraz MergeDate: Fri Apr 3 14:51:03 2026 (Merged from https://github.com/openssl/openssl/pull/29823)

Move typedef 'RSA_OEAP_PARAMS' to openssl/types.h

2026-02-18T13:09:46Z

This avoids redefinition of the type. CLA: trivial Reviewed-by: Shane Lontis Reviewed-by: Frederik Wedel-Heinen Reviewed-by: Paul Dale Reviewed-by: Tomas Mraz MergeDate: Wed Feb 18 13:09:26 2026 (Merged from https://github.com/openssl/openssl/pull/29994) (cherry picked from commit 5869303daaecf037f0d00dc33a00f9bdc1e71f2f)