github-actions[bot] opened a new issue, #3689:
URL: https://github.com/apache/iceberg-rust/issues/3689

   
   > Receive loop can spin after a truncated datagram
   
   | Details             |                                                |
   | ------------------- | ---------------------------------------------- |
   | Package             | `quinn-udp`                      |
   | Version             | `0.5.15`                   |
   | URL                 | 
[https://github.com/quinn-rs/quinn/commit/462865a6c33039c26076f7077c7cd7e2f997b9cd](https://github.com/quinn-rs/quinn/commit/462865a6c33039c26076f7077c7cd7e2f997b9cd)
 |
   | Date                | 2026-09-30                         |
   | Patched versions    | `>=0.5.16, <0.6.0,>=0.6.3`                  |
   
   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.
   
   See [advisory page](https://rustsec.org/advisories/RUSTSEC-2026-0538.html) 
for additional details.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to