Debian Patches

Status for openssl/3.0.19-1~deb12u2

Patch Description Author Forwarded Bugs Origin Last update
debian-targets.patch debian-targets Debian OpenSSL Team <pkg-openssl-devel@lists.alioth.debian.org> no 2017-11-05
man-section.patch man-section Debian OpenSSL Team <pkg-openssl-devel@lists.alioth.debian.org> no 2017-11-05
no-symbolic.patch no-symbolic Debian OpenSSL Team <pkg-openssl-devel@lists.alioth.debian.org> no 2017-11-05
pic.patch pic Debian OpenSSL Team <pkg-openssl-devel@lists.alioth.debian.org> no 2017-11-05
c_rehash-compat.patch also create old hash for compatibility Ludwig Nussel <ludwig.nussel@suse.de> no 2010-04-21
Configure-allow-to-enable-ktls-if-target-does-not-start-w.patch Configure: allow to enable ktls if target does not start with Linux
The Debian build system uses a `debian' target which sets CFLAGS and
then we have for instance debian-amd64 which inherits from
linux-x86_64 and debian. So far so good.

Since the target name does not start with `linux', the build system does not
enable ktls. So in order to get enabled, I
added a
`enable => [ "ktls" ],'
to the generic linux config which sets it explicit). Having this set, we can
check for it instead matching the target name.

This commit is based on changes for afalgeng in commit
9e381e8a01859 ("Configure: allow to enable afalgeng if target does not start with Linux")		 Sebastian Andrzej Siewior <sebastian@breakpoint.cc> no 2021-04-01
Remove-the-provider-section.patch Remove the provider section.
The provider section breaks libssl1.1 users. Remove it for now.		 Sebastian Andrzej Siewior <sebastian@breakpoint.cc> no 2022-06-08
conf-Serialize-allocation-free-of-ssl_names.patch conf: Serialize allocation/free of ssl_names.
The access to `ssl_names' is not fully serialized. With multiple threads
it is possible that more than one thread starts to clean up `ssl_names'.
This leads to occasional segfaults if more than one terminates and
performs the clean up.		 Sebastian Andrzej Siewior <sebastian@breakpoint.cc> no 2022-09-19
Fix-tests-for-new-default-security-level.patch Fix tests for new default security level
Fix tests that were expecting a default security level of 1 to work with
the new default of 2.

(Merged from https://github.com/openssl/openssl/pull/16760)		 Matt Caswell <matt@openssl.org> no 2021-10-05
dane_match_cert-should-X509_free-on-mcert-instead.patch dane_match_cert() should X509_free() on ->mcert instead of OPENSSL_free()


(Merged from https://github.com/openssl/openssl/pull/30250)

(cherry picked from commit 8b5cd6a682f0f6e7b8bf55137137c567d1899c4a)		 Alexandr Nedvedicky <sashan@openssl.org> no 2026-03-03
Fix-NULL-Dereference-When-Delta-CRL-Lacks-CRL-Number-Exte.patch Fix NULL Dereference When Delta CRL Lacks CRL Number Extension
Fixes CVE-2026-28388
Fixes https://github.com/openssl/srt/issues/77		 Daniel Kubec <kubec@openssl.org> no 2026-03-17
Added-test-for-CVE-2026-28388.patch Added test for CVE-2026-28388 Daniel Kubec <kubec@openssl.org> no 2026-03-17
Fix-NULL-deref-in-ec-dh_cms_set_shared_info.patch Fix NULL deref in [ec]dh_cms_set_shared_info
Multiple independent reports indicated a SIGSEGV was possible in CMS
processing when a crafted CMS EnvelopedData message using A Key
Agreement Recipient Info field. If the
KeyEncryptionAlgorithmIdentifier omits the optional parameter field, the
referenced functions above will attempt to dereference the
alg->parameter data prior to checking if the parameter field is NULL.

Confirmed to resolve the issues using the reproducers provided in the
security reports.


Fixes CVE-2026-28389		 Neil Horman <nhorman@openssl.org> no 2026-03-16
Test-for-DH-ECDH-CMS-KARI-processing-NULL-pointer-derefer.patch Test for DH/ECDH CMS KARI processing NULL pointer dereference
Test to ensure that, if we attempt to decrypt a CMS message with a
missing parameter field of KeyEncryptionAlgorithmIdentifier
we fail, rather than segfault.		 Neil Horman <nhorman@openssl.org> no 2026-03-31
Fix-NULL-deref-in-rsa_cms_decrypt.patch Fix NULL deref in rsa_cms_decrypt
Very simmilar to CVE-2026-28389, ensure that if we are missing
parameters in RSA-OAEP SourceFunc in CMS KeyTransportRecipientInfo,
we don't segfault when decrypting.


Fixes CVE-2026-28390		 Neil Horman <nhorman@openssl.org> no 2026-04-01
Add-test-for-CMS-decryption-with-RSA-keys.patch Add test for CMS decryption with RSA keys
Ensure we don't encounter a segfault when decrypting CMS messages with
malformed EnvelopedData when using RSA-OAEP.		 Neil Horman <nhorman@openssl.org> no 2026-03-29
Avoid-possible-buffer-overflow-in-buf2hex-conversion.patch Avoid possible buffer overflow in buf2hex conversion
Fixes CVE-2026-31789		 Igor Ustinov <igus68@gmail.com> no 2026-03-07
rsa_kem-validate-RSA_public_encrypt-result-in-RSASVE.patch rsa_kem: validate RSA_public_encrypt() result in RSASVE
RSA_public_encrypt() returns the number of bytes written on success and
-1 on failure. With the existing `if (ret)` check, a provider-side RSA KEM
encapsulation can incorrectly succeed when the underlying RSA public
encrypt operation fails. In that case the code reports success, returns
lengths as if encapsulation completed normally, and leaves the freshly
generated secret available instead of discarding it.

Tighten the success condition so RSASVE only succeeds when
RSA_public_encrypt() returns a positive value equal to the modulus-sized
output expected for RSA_NO_PADDING. Any other return value is treated as
failure, and the generated secret is cleansed before returning.

Fixes CVE: CVE-2026-31790		 Nikola Pajkovsky <nikolap@openssl.org> no 2026-03-19
rsa_kem-test-RSA_public_encrypt-result-in-RSASVE.patch rsa_kem: test RSA_public_encrypt() result in RSASVE
RSA_public_encrypt() returns the number of bytes written on success and
-1 on failure.

Add regression coverage in evp_extra_test using invalid RSA pubkey
which triggers -1 in RSA_public_encrypt() using encapsulation.		 Nikola Pajkovsky <nikolap@openssl.org> no 2026-03-23

All known versions for source package 'openssl'

Links