Advisory

RUSTSEC-2026-0538

Also known as: GHSA-6pp4-4cxf-xf88

Summary

Receive loop can spin after a truncated datagram

Details

Some targets read one datagram per recvmsg call instead of using recvmmsg: Apple platforms without the fast-apple-datapath feature, OpenBSD, NetBSD, Solaris and illumos, and from 0.6 also DragonFly BSD, Redox and GNU/Hurd. On these targets the receive loop set up its msghdr only once and looked at the MSG_TRUNC flag before checking whether recvmsg had failed. After a datagram larger than the receive buffer was dropped, a following EAGAIN still saw the old truncation flag. The loop then kept issuing non-blocking receives instead of returning WouldBlock.

When the receive buffer is smaller than a datagram that arrives, a remote sender can keep the task that drives the socket busy, before any QUIC packet authentication. The loop ends only when a later datagram fits in the buffer. Whether an application is exposed therefore depends on the receive buffer size it uses. Linux, Android, FreeBSD and Windows use other receive paths and are not affected.

The fix rebuilds the header before every recvmsg call and returns receive errors before checking the truncation flag. It is in 0.5.16 and 0.6.3.

Severity

Not rated by the source.

Dates

Published
2026-09-30 12:00 UTC
Modified
2026-11-13 12:45 UTC

Affected packages and fixes

quinn-udp

crates.io · All systems

Affected

  • introduced 0.0.0-0, fixed 0.5.16, introduced 0.6.0, fixed 0.6.3 (semver)

Fixed versions

0.5.16, 0.6.3

Fix

  • Fixed version 0.5.16
    cargo update -p quinn-udp --precise 0.5.16
  • Fixed version 0.6.3
    cargo update -p quinn-udp --precise 0.6.3

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences