OpenSSL QUIC: a peer withholding acknowledgements makes ACK-only metadata accumulate for the connection's life

Impact

OpenSSL stores transmit metadata for ACK-only packets even though the QUIC protocol never requires a peer to acknowledge them. A peer that completes a handshake, forces a stream of ACK-only responses by sending PING frames, and then withholds acknowledgements for ack-eliciting data causes that metadata to be retained for the lifetime of the connection. Growth is connection-scoped, so a single association is survivable; the risk is a client opening many concurrent QUIC connections and driving all of them the same way until the server exhausts memory. On a fleet the concern is a QUIC-fronted gateway or storage endpoint whose OOM kill lands on a shared node rather than on the abusive client.

Who can reach it

A remote peer that can complete a QUIC handshake with the OpenSSL endpoint. Protocol-level handshake completion is required, but no application-level credential; effect scales with the number of connections the attacker is allowed to open.

What to do

Upgrade to the fixed OpenSSL release named in the 2026-08-25 advisory and restart QUIC-serving processes. Only the OpenSSL QUIC stack is affected. Until then, per-source connection limits and idle timeouts on the QUIC listener bound how much memory one client can pin, and a memory cgroup limit on the service keeps an OOM from taking neighbours with it. The record does not name a fixed version for this CVE.

References

Related entries

• OpenSSL CMP: unchecked protectionAlg parameter type is dereferenced as a PBMParameter and crashes the processCVE-2026-63076 · OpenSSL CMP password-based MAC verification (protectionAlg parameter type check)High
• Linux kernel SMC-D client (CHID matching against unpopulated ism_dev slot): Slot 0 of the client's ISM device array isCVE-2026-64048 · Linux kernel SMC-D client (CHID matching against unpopulated ism_dev slot)High
• Linux kernel libceph: a monmap advertising zero monitors hits a BUG_ON and takes down the client nodeCVE-2026-68155 · Linux kernel libceph (ceph_monmap_decode, zero-monitor monmap)High
• Linux kernel libceph: NULL dereference in CRUSH locality lookup when a parent bucket's type name is missingCVE-2026-68157 · Linux kernel libceph (get_immediate_parent CRUSH type name lookup)High
• Linux kernel (net/tls): A remote peer sends a zero-length TLS 1.3 application_data record - which the RFC explicitlyCVE-2026-72330 · Linux kernel (net/tls)High
• Linux kernel (drivers/nvme/target): A client that completes the TLS handshake against the NVMe-oF TCP target and thenCVE-2026-74385 · Linux kernel (drivers/nvme/target)High