Skip to content

← Actionable
Unrated

Receive loop can spin after a truncated datagram

GHSA-6pp4-4cxf-xf88

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (quinn-udp 0.6.3, 0.5.16), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • crates.io quinn-udp

    Affected
    >= 0.0.0-0, < 0.5.16>= 0.6.0, < 0.6.3
    Fixed in
    0.5.16, 0.6.3

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from osv record RUSTSEC-2026-0538

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-6pp4-4cxf-xf88

Advisory: Receive loop can spin after a truncated datagram
IDs: GHSA-6pp4-4cxf-xf88
Record: https://patchnext.com/advisories/rustsec-2026-0538 (revision 1, source checked 14 Nov 2026, 08:25 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: quinn-udp 0.6.3, 0.5.16. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io quinn-udp: affected >= 0.0.0-0, < 0.5.16; >= 0.6.0, < 0.6.3; fixed in 0.5.16, 0.6.3

## Suggested inspection (read-only)
- crates.io quinn-udp: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on quinn-udp.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/RUSTSEC-2026-0538 (OSV record RUSTSEC-2026-0538 lists affected ranges: crates.io quinn-udp >=0.0.0-0 =0.6.0 <0.6.3 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…