https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 28 Sep 2026 23:33:24 +0000 https://vulnerability.circl.lu/vuln/cve-2026-97618 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>io_uring/net: don&#39;t overconsume buffers when using MSG_TRUNC</p> <p>When a recv/recvmsg is issued with MSG_TRUNC and the incoming packet is larger than the provided buffer, the net layer returns the full length of the packet rather than the number of bytes actually copied into the buffer. As a result, io_uring advances more of the provided buffer ring than was actually filled. Use the actual filled region size to consume the buffer, but still return the full size to preserve MSG_TRUNC semantics.</p> <p>Take care with multishot, because that seems to already truncate the consumption based on the available payload size.</p> <p>This was reported in https://github.com/axboe/liburing/issues/1619.</p> <p>[axboe: fold in size_t unsigned fix]</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>io_uring/net: don&#39;t overconsume buffers when using MSG_TRUNC</p> <p>When a recv/recvmsg is issued with MSG_TRUNC and the incoming packet is larger than the provided buffer, the net layer returns the full length of the packet rather than the number of bytes actually copied into the buffer. As a result, io_uring advances more of the provided buffer ring than was actually filled. Use the actual filled region size to consume the buffer, but still return the full size to preserve MSG_TRUNC semantics.</p> <p>Take care with multishot, because that seems to already truncate the consumption based on the available payload size.</p> <p>This was reported in https://github.com/axboe/liburing/issues/1619.</p> <p>[axboe: fold in size_t unsigned fix]</p> https://vulnerability.circl.lu/vuln/cve-2026-97618