Bug 2506060 - CVE-2026-16318 s2n-tls: s2n-tls: Denial of Service due to memory leak in QUIC transport parameters handler [epel-all]
Summary: CVE-2026-16318 s2n-tls: s2n-tls: Denial of Service due to memory leak in QUIC...
Keywords:
Status: NEW
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: s2n-tls
Version: epel10
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Orphan Owner
QA Contact:
URL:
Whiteboard: {"flaws": ["915fdb46-fe65-4ecb-9c02-6...
Depends On:
Blocks: CVE-2026-16318
TreeView+ depends on / blocked
 
Reported: 2026-07-22 11:07 UTC by TEJ RATHI
Modified: 2026-07-22 11:07 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description TEJ RATHI 2026-07-22 11:07:25 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

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


Note You need to log in before you can comment on or make changes to this bug.