GPU VulnDB

Database/Kernel, userspace & hypervisor

OpenSSL: QUIC server keeps rejected streams after peer reset, causing unbounded memory growth

CVSS 7.5CVE-2026-124709Kernel, userspace & hypervisorcurated

Impact

When an OpenSSL QUIC server rejects a stream the peer opened, and the peer resets that stream before the rejection is sent, the stream's state is never collected, even though the peer gets its stream credit back. A client that completes a handshake and keeps a connection open can keep opening and resetting streams, growing server memory by about 300 bytes per stream until the process runs out of memory and every connection on it drops. The default configuration reaches this path once the connection has a default stream. Growth is slow and there is no memory corruption or disclosure. OpenSSL rates it Low.

Who can reach it

Any remote client that can complete a QUIC handshake with a server built on OpenSSL's QUIC implementation. It needs a long-lived connection. No application-level authentication is implied.

What to do

Update OpenSSL to the release named in the 2026-11-17 OpenSSL advisory, or to a distro package carrying the listed commits, then restart the QUIC-serving processes. No reboot is needed. Most fleet daemons do not run OpenSSL's QUIC server, so first check whether anything on the node does.

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.