Skip to content
OpenAdvisories
Medium · 5.3 CVE-2026-16318 EUVD-2026-46402

QUIC Transport Parameters Memory Leak During HelloRetryRequest in s2n-tls

Published Jul 21, 2026 · Updated Jul 22, 2026 · Assigned by AMZN

Description

The QUIC transport parameters extension handler in s2n-tls incorrectly uses s2n_alloc instead of s2n_realloc to store the peer's transport parameters. When a TLS 1.3 connection goes through a HelloRetryRequest, the handler is called twice on the same connection. On the second call, s2n_alloc zeroes the existing pointer before allocating new memory, causing the first allocation to be leaked.

This can occur during normal QUIC traffic when a client offers a key share group the server does not prefer. An unauthenticated user can amplify the issue by deliberately forcing HelloRetryRequests, causing up to approximately 64 KB of unreachable memory per handshake. Over time, this can lead to increased memory consumption on long-running server processes. The unreachable memory is only reclaimed when the process is restarted.

Only server-side QUIC-enabled deployments are affected. Non-QUIC TLS connections are not affected.

We recommend you upgrade s2n-tls to version v1.7.6

Affected products

VendorProductAffectedFixed
Amazon s2n-tls ≤ v1.7.5 —

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

ReleasePackageFixed inAdvisory
SLES 15 SP7 aws-efs-utils 3.3.4-150600.17.12.1 SUSE-SU-2026:5101-1
SLES 15 SP6 aws-efs-utils 3.3.4-150600.17.12.1 SUSE-SU-2026:5101-1
ReleasePackageFixed inAdvisory
openSUSE Tumbleweed aws-efs-utils 3.2.0-1.1 openSUSE-SU-2026:11492-1
openSUSE Tumbleweed s2n 1.7.7-1.1 openSUSE-SU-2026:11526-1
openSUSE Leap 16.0 s2n 1.5.1-bp160.2.1 openSUSE-SU-2026:21501-1

Advisories 4

References