Database/Kernel, userspace & hypervisor
OpenSSL: NULL dereference in SSL_check_chain crashes TLS 1.3 peers
Impact
Any peer in a TLS 1.3 handshake can send an unrecognised signature algorithm in the signature_algorithms_cert extension and crash an application that calls SSL_check_chain() during or after the handshake. The affected process dies outright, so for a server-side service this is a remote unauthenticated crash loop and for a client it is a hang-free but fatal abort. On a GPU fleet the practical exposure is whichever TLS endpoints and node-local daemons are built against OpenSSL 1.1.1d-1.1.1f and use that callback path - a narrow set, since only applications calling SSL_check_chain are affected. No data is exposed; the vector is availability-only. Versions before 1.1.1d are not affected.
Who can reach it
Any TLS 1.3 peer that the vulnerable application talks to - a remote client against an exposed listener, or a malicious server against an outbound connection. No authentication required.
What to do
Update to OpenSSL 1.1.1g or the equivalent distribution package (openSUSE, Debian, FreeBSD 12.1 all shipped updates). Restart every service that has the shared library mapped; nothing here needs firmware work or a node drain, but a process restart is mandatory for the fix to take effect.
References
Related entries
- QEMU (virtio-net): Heap use-after-free in virtio_net_receive_rcu - guest-to-host code execution in the QEMU processCVE-2021-3748 · QEMU (virtio-net)High
- Linux kernel (drivers/nvme/target): When the target's peer-to-peer memory pool runs dry, it still tries to return theCVE-2021-47130 · Linux kernel (drivers/nvme/target)High
- QEMU (virtio-net): Map leaking on error during receive - guest-triggered host memory exhaustion / DoSCVE-2022-26353 · QEMU (virtio-net)High
- OpenSSL 3.0: X.509 email-address punycode buffer overflow (4-byte stack overflow)CVE-2022-3602 · OpenSSL 3.0High
- OpenSSL 3.0: X.509 email-address variable-length buffer overflow (DoS)CVE-2022-3786 · OpenSSL 3.0High
- AMD CPU (Sinkclose): Sinkclose: SMM lock bypassCVE-2023-31315 · AMD CPU (Sinkclose)High
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.