GPU VulnDB

Database/Kernel, userspace & hypervisor

OpenSSL DTLS: out-of-sequence handshake fragments each allocate a full-length reassembly buffer, memory amplification

CVSS 5.3CVE-2026-95690Kernel, userspace & hypervisorcurated

Impact

A peer can send crafted out-of-sequence DTLS handshake fragments. OpenSSL then allocates a reassembly buffer the size of the full claimed message length for each buffered message, so a small amount of traffic ties up a large amount of memory in the DTLS-serving process. This exhausts memory and does not corrupt it. The record does not describe any confidentiality or integrity impact. It only matters for services that terminate DTLS over UDP, such as DTLS-based VPN or telemetry endpoints. Plain TLS over TCP is not described as affected.

Who can reach it

Any network peer that can send UDP to a DTLS-terminating service and begin a handshake. No authentication needed.

What to do

Fixed upstream in the OpenSSL pull requests referenced. The record does not list fixed release versions, so track the OpenSSL security advisory and your distribution's openssl package. Then restart every process that serves DTLS, because the library is loaded at process start. Until then, rate-limiting or capping concurrent DTLS associations limits how much memory can be pinned.

References

Related entries

All Kernel, userspace & hypervisor entries

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.