Neil Horman dc10ffc283 Fix potential use-after-free in REF_PRINT_COUNT ... We use REF_PRINT_COUNT to dump out the value of various reference counters in our code However, we commonly use this macro after an increment or decrement. On increment its fine, but on decrement its not, because the macro dereferences the object holding the counter value, which may be freed by another thread, as we've given up our ref count to it prior to using the macro. The rule is that we can't reference memory for an object once we've released our reference, so lets fix this by altering REF_PRINT_COUNT to accept the value returned by CRYPTO_[UP|DOWN]_REF instead. The eliminates the need to dereference the memory the object points to an allows us to use the call after we release our reference count Reviewed-by: Richard Levitte <levitte@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/25664)		2024-12-10 14:58:08 +01:00
..
crypto	Add CTX copy function for EVP_MD to optimize the performance of EVP_MD_CTX_copy_ex.	2024-11-20 14:12:53 +01:00
internal	Fix potential use-after-free in REF_PRINT_COUNT	2024-12-10 14:58:08 +01:00
openssl	A typo fix in a comment	2024-12-06 15:31:35 +01:00