Bug 2578087

Summary: CVE-2026-95691 erlang: openssl: Denial of Service via overlapping QUIC CRYPTO frame processing [fedora-all]
Product: [Fedora] Fedora Reporter: Srikanth Balasubramanian <sbalasub>
Component: erlangAssignee: Peter Lemenkov <lemenkov>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: jonathan, lemenkov, rhbugs, rich
Target Milestone: ---Keywords: Security, SecurityTracking
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: {"flaws": ["92ad44b1-7161-4484-8a24-1c749b5a6f29"]}
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-11-20 12:25:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2570988    

Description Srikanth Balasubramanian 2026-11-20 11:39:48 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.

Issue summary: A retransmitted QUIC CRYPTO frame can release packet storage
while the TLS record layer retains a direct pointer into that storage causing
use after free.

Impact summary: A malicious QUIC server can cause a heap-use-after-free read
in the OpenSSL QUIC client. The server can also identify one allocator-adjacent
byte through the client's protected Handshake response.

CWE: CWE-416: Use After Free

Description: During CRYPTO stream processing, a pointer into the first frame's
memory on the stream is lent to the TLS handshake processing. The memory
must remain stable until it is processed and released. However the processing
of retransmitted CRYPTO frames could release the memory if the retransmitted
frame fully overlapped the existing frame. This then causes use-after-free read
when the TLS handshake processing continues.

The use-after-free read can lead to a Denial-of-Service of the client
application or a minor leak of information about the heap memory contents
that might be overwritten with other data, subsequently allocated by
the application, to the peer.

FIPS impact: no
The FIPS module is not affected as the QUIC implementation is outside of
the OpenSSL FIPS module boundary.

Comment 1 Peter Lemenkov 2026-11-20 12:25:12 UTC
erlang is not affected by CVE-2026-95691.

This flaw is in OpenSSL's QUIC CRYPTO frame processing (denial of service via overlapping frames). Erlang/OTP neither ships nor exercises that code:

- The crypto and ssl applications link against the *system* OpenSSL (BuildRequires: pkgconfig(openssl)); any fix for CVE-2026-95691 is delivered by the openssl package.
- OTP's TLS/DTLS stack (the ssl application) is implemented in Erlang and does not use OpenSSL's QUIC code; OTP exposes no OpenSSL QUIC interface at all.
- The only OpenSSL code *bundled* in OTP (Provides: bundled(openssl) = 3.1.4) is a very small part of the MD5 digest — erts/emulator/openssl/ holds only crypto/md5/md5_dgst.c, crypto/md5/md5_local.h, include/crypto/md32_common.h and include/openssl_local/md5.h (see erts/emulator/openssl/README). No QUIC code is bundled.

The vulnerable code path therefore does not exist in Erlang/OTP. Closing as NOTABUG (not affected).