Allocation of Resources Without Limits or Throttling Affecting rust-bootupd package, versions <0:0.3.2-1.1.hum1


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.27% (20th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL10-RUSTBOOTUPD-22696040
  • published21 Nov 2026
  • disclosed18 Nov 2026

Introduced: 18 Nov 2026

NewCVE-2026-95690  (opens in a new tab)
CWE-770  (opens in a new tab)

How to fix?

Upgrade RHEL:10 rust-bootupd to version 0:0.3.2-1.1.hum1 or higher.
This issue was patched in RHSA-2026:80572.

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-bootupd package and not the rust-bootupd package as distributed by RHEL. See How to fix? for RHEL:10 relevant fixed versions and status.

Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory.

Impact summary: A remote attacker can send a few small crafted DTLS handshake fragments to make a DTLS server or client allocate well over a megabyte of memory per connection, which may lead to memory exhaustion and Denial of Service if many connections are made.

CWE: CWE-770: Allocation of Resources Without Limits or Throttling

Description: DTLS handshake messages can arrive out of order and fragmented, so OpenSSL buffers fragments of up to ten out-of-sequence messages until reassembly is possible. When the first fragment of a new message arrives, OpenSSL allocates a buffer sized to the full message length declared in the fragment header, plus a reassembly bitmap, instead of storing only the bytes actually received. The declared length is capped by the maximum certificate list size, 128KB by default, and that cap applies to every handshake message type rather than only to Certificate messages.

Only DTLS endpoints reach this code. TLS, QUIC and applications that do not use DTLS are unaffected. An attacker sends fragments that declare a large message length but carry almost no data, using up to ten distinct message sequence numbers.

A single connection can then hold roughly 1.4MB of buffers from about 156 bytes on the wire. Because the number of buffered messages is capped, memory exhaustion requires many connections or many peers, which is why the severity is Low.

FIPS impact: no The affected code is outside the FIPS module boundary.

CVSS Base Scores

version 3.1