GPU VulnDB

Database/Kernel, userspace & hypervisor

OpenSSL QUIC: retransmitted NEW_CONNECTION_ID frames queue unbounded RETIRE frames, exhausting memory

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

Impact

A malicious QUIC peer can make an OpenSSL-based QUIC endpoint queue RETIRE_CONNECTION_ID frames without limit, driving the process out of memory and taking it down. This is an incomplete fix for CVE-2026-84784: the earlier patch did not ignore retransmitted NEW_CONNECTION_ID frames. Only applications that use OpenSSL's own QUIC implementation are affected. TLS over TCP is not, and the FIPS module is not affected. On a GPU node the risk is an OOM event that can also hit co-located workloads if the affected service has no memory limit. Confidentiality and integrity are not affected.

Who can reach it

Any remote peer that can complete a QUIC exchange with a service built on OpenSSL's QUIC stack. No authentication needed.

What to do

Upgrade OpenSSL to a release that includes the fix referenced in openssl/openssl PR 33544 and restart every process that links it. Distro packages usually need a restart of the dependent daemons, not a reboot. The record does not list fixed version numbers, so check your distribution's advisory. Find out first whether any service actually uses OpenSSL QUIC. Most datacenter services do not, and those can wait for normal patch cadence.

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.