openssl/fuzz, branch openssl-3.6

Copyright year updates

2026-08-25T11:46:17Z

Reviewed-by: Neil Horman Reviewed-by: Milan Broz MergeDate: Tue Aug 25 11:46:18 2026 Release: yes

fuzz/provider.c: check evp##_up_ref return value in collect_##evp

2026-08-18T05:24:56Z

Coverity has reported an unchecked result of an evp##_up_ref call that is checked elsewhere. Rewrite the collect routine to try to do the up_ref first, and then call free if push doesn't succeed. Resolves: https://scan5.scan.coverity.com/#/project-view/65248/10222?selectedIssue=1695451 Resolves: https://scan5.scan.coverity.com/#/project-view/65248/10222?selectedIssue=1695454 Fixes: f3b988dc2951 "Add provider fuzzer" Reviewed-by: Viktor Dukhovni Reviewed-by: Tomas Mraz Merge-date: Tue Aug 18 05:24:16 2026 Merged-from: https://github.com/openssl/openssl/pull/32348 (cherry picked from commit e15e4852b3d4776b7aeb827ba734f2ac7a0b1ff7)

Copyright year updates

2026-06-09T11:44:35Z

Reviewed-by: Neil Horman Reviewed-by: Saša Nedvědický MergeDate: Tue Jun 9 11:44:36 2026 Release: yes

Fix broken hex data by reformatting

2026-06-03T08:46:34Z

The clang format broke some data in hexadecimal format. To make the tool obedient, the trailing comma needs to be removed, then it interpretes the data differently and therefore does not reformat it. The format can then be changed to the correct form. Fixes: https://github.com/openssl/project/issues/1959 Signed-off-by: Norbert Pocs Reviewed-by: Milan Broz Reviewed-by: Eugene Syromiatnikov MergeDate: Wed Jun 3 08:47:16 2026 (Merged from https://github.com/openssl/openssl/pull/31350)

Fix legitimate spelling errors

2025-12-21T08:15:33Z

Reviewed-by: Neil Horman Reviewed-by: Tomas Mraz (Merged from https://github.com/openssl/openssl/pull/29459)

3.6-POST-CLANG-FORMAT-WEBKIT

2025-12-09T08:00:43Z

Reviewed-by: Saša Nedvědický Reviewed-by: Neil Horman Reviewed-by: Nikola Pajkovsky (Merged from https://github.com/openssl/openssl/pull/29245)

Reduce Max number of commands handled per fuzzer pass in quic-lcidm.

2025-10-04T08:29:39Z

We've gotten a few recent reports of a hang in the quic-lcidm fuzzer: https://issues.oss-fuzz.com/issues/448510502 It looks pretty straightforward (I think). The fuzzer input buffer is used in this particular case to randomly issue commands to the lcidm hash table (add/delete/query/flush/etc). The loop for the command processing (based on the input buffer), is limited to 10k commands. However the fuzzer will on occasion provide very large buffers (500k) which easily saturate that limit. If the input buffer happens to do something like get biased toward mostly additions, we wind up with a huge hashtable that has to constantly grow and rehash, which we've seen leads to timeouts in the past. Most direct fix I think here, given that this is something of an artificial failure in the fuzzer, is to simply clamp the command limit more. Fixes openssl/project#1664 Reviewed-by: Kurt Roeckx Reviewed-by: Matt Caswell Reviewed-by: Tomas Mraz (Merged from https://github.com/openssl/openssl/pull/28724) (cherry picked from commit 01c7958f2359e951a95350affb6b178fb50fed03)

Copyright year updates

2025-09-02T13:05:45Z

Reviewed-by: Neil Horman Reviewed-by: Saša Nedvědický Release: yes

Fix failure checking on rcu_read_lock

2025-08-09T13:22:13Z

during memfail testing: https://github.com/openssl/openssl/actions/runs/16794088536/job/47561223902 We get lots of test failures in ossl_rcu_read_lock. This occurs because we have a few cases in the read lock path that attempt mallocs, which, if they fail, trigger an assert or a silent failure, which isn't really appropriate. We should instead fail gracefully, by informing the caller that the lock failed, like we do for CRYPTO_THREAD_read_lock. Fortunately, these are all internal apis, so we can convert ossl_rcu_read_lock to return an int indicating success/failure, and fail gracefully during the test, rather than hitting an assert abort. Fixes openssl/project#1315 Reviewed-by: Paul Yang Reviewed-by: Dmitry Belyavskiy Reviewed-by: Paul Dale (Merged from https://github.com/openssl/openssl/pull/28195)

apps, fuzz, providers: use array memory (re)allocation routines

2025-08-08T16:22:10Z

Co-Authored-by: Alexandr Nedvedicky Signed-off-by: Eugene Syromiatnikov Reviewed-by: Saša Nedvědický Reviewed-by: Matt Caswell Reviewed-by: Paul Dale Reviewed-by: Neil Horman (Merged from https://github.com/openssl/openssl/pull/28059)