Issue summary: When OpenSSL processes QUIC traffic from a peer that repeatedly sends ack-eliciting packets while not acknowledging ACK-only responses, the QUIC stack can retain ACK-only packet metadata for the lifetime of the connection. Impact summary: A remote peer that can complete a QUIC handshake can cause connection-scoped memory growth which may lead to Denial of Service through memory exhaustion, especially with sustained traffic or many concurrent QUIC connections. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: When the OpenSSL QUIC stack sends an ACK-only packet, there is no requirement by the QUIC protocol that the peer will acknowledge that ACK-only packet (i.e. it is itself not ack-eliciting). However, the OpenSSL implementation stores the metadata about the ACK frames regardless. In and of itself that's ok, but if a malicious peer establishes a connection, and then drives the connection such that ACK-only packets are forced from the OpenSSL implementation peer (i.e., by sending numerous PING frames), and then withholding any subsequent acks for ack-eliciting data, like legitimate data, said malicious peer can force inappropriate memory growth on the OpenSSL peer, potentially leading to a Denial of Service. The fix is to ensure that we account for the transmission of the ACK-only packet in the packet histories high and low watermark without actually storing the ACK-only packet metadata itself. FIPS impact: no The OpenSSL FIPS module is not affected as the QUIC code is outside the FIPS module boundary.
{
"binaries": [
{
"binary_name": "efi-shell-aa64",
"binary_version": "2025.11-3ubuntu7"
},
{
"binary_name": "efi-shell-loongarch64",
"binary_version": "2025.11-3ubuntu7"
},
{
"binary_name": "efi-shell-riscv64",
"binary_version": "2025.11-3ubuntu7"
},
{
"binary_name": "efi-shell-x64",
"binary_version": "2025.11-3ubuntu7"
},
{
"binary_name": "ovmf",
"binary_version": "2025.11-3ubuntu7"
},
{
"binary_name": "ovmf-amdsev",
"binary_version": "2025.11-3ubuntu7"
},
{
"binary_name": "ovmf-generic",
"binary_version": "2025.11-3ubuntu7"
},
{
"binary_name": "ovmf-inteltdx",
"binary_version": "2025.11-3ubuntu7"
},
{
"binary_name": "ovmf-legacy",
"binary_version": "2025.11-3ubuntu7"
},
{
"binary_name": "qemu-efi-aarch64",
"binary_version": "2025.11-3ubuntu7"
},
{
"binary_name": "qemu-efi-loongarch64",
"binary_version": "2025.11-3ubuntu7"
},
{
"binary_name": "qemu-efi-riscv64",
"binary_version": "2025.11-3ubuntu7"
}
],
"priority_reason": "OpenSSL developers have rated this low severity"
}{
"binaries": [
{
"binary_name": "efi-shell-aa64-hwe",
"binary_version": "2025.11-3ubuntu8"
},
{
"binary_name": "efi-shell-loongarch64-hwe",
"binary_version": "2025.11-3ubuntu8"
},
{
"binary_name": "efi-shell-riscv64-hwe",
"binary_version": "2025.11-3ubuntu8"
},
{
"binary_name": "efi-shell-x64-hwe",
"binary_version": "2025.11-3ubuntu8"
},
{
"binary_name": "ovmf-amdsev-hwe",
"binary_version": "2025.11-3ubuntu8"
},
{
"binary_name": "ovmf-generic-hwe",
"binary_version": "2025.11-3ubuntu8"
},
{
"binary_name": "ovmf-hwe",
"binary_version": "2025.11-3ubuntu8"
},
{
"binary_name": "ovmf-inteltdx-hwe",
"binary_version": "2025.11-3ubuntu8"
},
{
"binary_name": "ovmf-legacy-hwe",
"binary_version": "2025.11-3ubuntu8"
},
{
"binary_name": "qemu-efi-aarch64-hwe",
"binary_version": "2025.11-3ubuntu8"
},
{
"binary_name": "qemu-efi-loongarch64-hwe",
"binary_version": "2025.11-3ubuntu8"
},
{
"binary_name": "qemu-efi-riscv64-hwe",
"binary_version": "2025.11-3ubuntu8"
}
],
"priority_reason": "OpenSSL developers have rated this low severity"
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "libssl3t64",
"binary_version": "3.5.5-1ubuntu3.4"
},
{
"binary_name": "openssl",
"binary_version": "3.5.5-1ubuntu3.4"
},
{
"binary_name": "openssl-provider-legacy",
"binary_version": "3.5.5-1ubuntu3.4"
}
],
"priority_reason": "OpenSSL developers have rated this low severity"
}