openssl/ssl
Neil Horman 389728876b set SSLfatal if tls1_set_shared_sigalgs has a malloc failure
Detected another memfail failure

https://github.com/openssl/openssl/actions/runs/16926186604/job/47962169870

Tracking it back, it occurs because tls1_set_server_sigalgs attempts to
preform an allocation, and in the event of failure, returns 0 without
setting SSLfatal, like the other failure paths in this function do when
returning 0, which translates to a return of WORK_ERROR higher up the
stack

The result is that on the next call to check_fatal in
read_state_machine, we fail the assert when deubg is enabled (as it is
in the coverage tests).

Fix it by calling SSLfatal when the call to OPENSSL_calloc fails in this
function.

Reviewed-by: Saša Nedvědický <sashan@openssl.org>
Reviewed-by: Kurt Roeckx <kurt@roeckx.be>
Reviewed-by: Matt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/28250)
2025-08-15 08:39:11 -04:00
..
quic Add CRYPTO_FREE_REF to ossl_quic_free_token_store 2025-08-14 11:19:52 -04:00
record ssl: use array memory (re)allocation routines 2025-08-08 12:22:10 -04:00
rio
statem ssl: use array memory (re)allocation routines 2025-08-08 12:22:10 -04:00
bio_ssl.c
build.info
d1_lib.c
d1_msg.c
d1_srtp.c
methods.c
pqueue.c
priority_queue.c ssl: use array memory (re)allocation routines 2025-08-08 12:22:10 -04:00
s3_enc.c
s3_lib.c
s3_msg.c
ssl_asn1.c
ssl_cert.c ssl: use array memory (re)allocation routines 2025-08-08 12:22:10 -04:00
ssl_cert_comp.c
ssl_cert_table.h
ssl_ciph.c ssl: use array memory (re)allocation routines 2025-08-08 12:22:10 -04:00
ssl_conf.c
ssl_err_legacy.c
ssl_init.c
ssl_lib.c ssl: use array memory (re)allocation routines 2025-08-08 12:22:10 -04:00
ssl_local.h
ssl_mcnf.c
ssl_rsa.c
ssl_rsa_legacy.c
ssl_sess.c
ssl_stat.c
ssl_txt.c
ssl_utst.c
t1_enc.c
t1_lib.c set SSLfatal if tls1_set_shared_sigalgs has a malloc failure 2025-08-15 08:39:11 -04:00
t1_trce.c
tls13_enc.c Assert SSLFatal on keylog failure 2025-08-12 14:15:50 -04:00
tls_depr.c
tls_srp.c