Skip to content
VulniPulse
Advisory severityHigh7.5Vendor: MediumRed Hat Linux

High [CVE-2026-18798] QUIC server may trigger double free when processing INITIAL packet

This high-severity Red Hat Linux advisory covers CVE-2026-18798 affecting Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 9, Cert Manager support for Red Hat OpenShift release 1.20.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-18798 Source published Source updated

VulniPulse record published Record updated

Affected products & platforms
Red Hat LinuxRed Hat Enterprise Linux
Open source advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

Issue summary: QUIC server may double free QRX (QUIC record layer RX) object when channel creation fails for initial packet. Impact summary: Double free leads to heap corruption, which typically results in termination of QUIC server process, leading to Denial of Service.

There is so far no evidence that this double free is exploitable for remote code execution, thus it is considered highly improbable. CWE: CWE-415: Double Free Description: In order to validate initial packet, OpenSSL QUIC stack default packet handler (port_default_packet_handler()) creates a so-called QRX object.

If the initial packet validates successfully with QRX object, the default packet handler proceeds to channel (connection object) creation. The QRX object used for packet validation is passed to port_bind_channel(), so it becomes part of the newly created connection.

If port_bind_channel() fails, then it also frees the QRX object. Once port_bind_channel() returns, the port_default_packet_handler() detects the failure and proceeds to the error branch, where the same QRX object is freed for the second time.

The failure in port_bind_channel() function can be induced with a relatively low effort by a malformed (non RFC 9000 compliant) INITIAL packet.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.

Official advisory · high-confidence parse· fetched 8 days ago·verify at source

Fixed versions
  • openssl-1:3.5.8-1.el10_2
  • openssl-1:3.5.8-1.el9_8
  • cert-manager/jetstack-cert-manager-rhel9:1790223279
  • cert-manager/cert-manager-istio-csr-rhel9:1790223719
  • cert-manager/cert-manager-operator-rhel9:1790272426
  • cert-manager/jetstack-cert-manager-acmesolver-rhel9:1790589998
  • cert-manager/jetstack-cert-manager-rhel9:1790589912
  • cert-manager/cert-manager-istio-csr-rhel9:1790589914
  • cert-manager/cert-manager-operator-rhel9:1790589855
  • openssl3-main-3.5.8-0.1.hum1
  • openssl-main-3.5.8-0.1.hum1
  • rhui5/cds-kubernetes-rhel9:1789479916
  • rhui5/installer-rhel9:1789482961
  • rhui5/cds-rhel9:1790241954
  • rhui5/haproxy-rhel9:1790241900
  • rhui5/rhua-rhel9:1790242004
  • RHSA-2026:67154
  • RHSA-2026:67165
  • RHSA-2026:72394
  • RHSA-2026:72395
  • RHSA-2026:72399
  • RHSA-2026:72470
  • RHSA-2026:72475
  • RHSA-2026:72476
  • RHSA-2026:59635
  • RHSA-2026:59641
  • RHSA-2026:67956
  • RHSA-2026:71603

Official advisory · high-confidence parse· fetched 8 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Official advisory · high-confidence parse· fetched 8 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.